Roadmap#

TideTracker is in active development as a solo-developer beta. This page reflects the current direction of the work. It's intentionally undated — priorities shift based on what beta users report, what the correction engine reveals, and what genuinely needs to ship before anything else.

Now — in the app#

• Site-specific tide and current predictions for Puget Sound and Strait of Juan de Fuca dive sites
• NOAA CO-OPS data pipeline with subordinate-station offset handling
• Correction engine with IQR-filtered applied delta
• Day rating on the briefing hero and on each day's card in date-range mode (Good / Marginal / Poor)
• Window quality badges on slack windows (Best / Good / Marginal / Skip)
• Confidence tiers on each site, grounded in observation count (Low / Moderate / High)
• Staleness flagging for corrections older than 12 months
• Per-metric NOAA station tagging in the briefing and on the wizard's site/date steps
• Calendar-based site planning
• User accounts with email/password authentication, verification, and password reset
• In-app feedback form

Near-term — actively in progress or next up#

• Weather integration — surface-conditions layer for wind, barometric pressure, and river outflow
• Wiring more dive-log fields into the correction engine — the Log a dive form already captures slack delta, observed current strength, prediction-accuracy rating, and free-text notes. Today only the slack delta feeds the correction engine. Near-term work will fold current-strength observations and prediction-accuracy ratings into the per-site correction signal.
• User guide and documentation — what you're reading now
• Manual station selection — for users who want to override the default station mapping at a given site
• Dark mode
• Date range picker with best-dive-day highlighting across the range

Mid-term — planned, not yet in development#

• Trajectory indicator — improving / stable / declining signal for site corrections over time
• Moderator accounts — trusted local divers with tools to flag and weight reports at sites they know well
• Privacy policy and terms pages
• Public changelog driven by semantic version tags

Long-term — directional, not promised#

• Remote sensor network — standalone pressure and current loggers at sites distant from NOAA stations or showing low correction confidence. Deployment prioritized by geographic and hydrologic distance from reference stations, correction-model confidence, and user-reported discrepancies.
• OAuth sign-in — additive, no migration risk
• Geodex integration — read-only dive-site API for a sister project focused on species sightings and underwater photography, with cross-app data enrichment between dive conditions and sightings. Intentionally separated from the core TideTracker backlog.
• Regional expansion beyond the Salish Sea
• Tech-diving section — invite-only access to deeper-water content, gas-planning context, and tech-specific site notes. Directional, not promised.

How priorities get set#

Three signals drive what moves up:

1. Safety-relevant gaps. Anything that causes users to misjudge conditions in ways that could put them at risk gets prioritized over everything else.
2. User reports. Patterns in feedback — missing sites, systematically wrong predictions, friction in key workflows — drive the next round of work.
3. Correction confidence. Sites where the engine is least confident, and features that would sharpen that confidence, rank high.

If you want something on this list or higher up it, the feedback form is the fastest way to influence priorities.