The Dibber roadmap

Improve file uploads and supported account connections. Direct watch integrations depend on access granted by the watch companies, so this doesn't include a promise of Garmin auto-upload.

Make large tracks and map images easier to work with, improve recovery from interrupted imports, and fix awkward steps on smaller screens. This isn't a promise of offline use; the aim is fewer interruptions in the existing workflow.

Open a finished example in guest mode before uploading anything. See how the map, leg analysis and exports fit together using a real race with permission to show its map. A clearly labelled synthetic-map example is already browsable at the sample race while that permission is arranged.

See which legs cost the most time in one table. Recorded times stay separate from estimated losses, and every estimate names what it is compared against: the time you were expected to do, and — where the race's results are imported — the best split recorded on that leg. A leg where you beat the reference shows as time gained.

Bring races, distances and tagged mistakes into one view, with comparisons across years: pick a year and see how it stacks up against the last. The season stats on the home page become one block inside it, and every time-loss total keeps showing the calculation behind it.

Improve performance, keyboard and touch controls, and accessibility before removing the beta label. The release target shouldn't take priority over fixing a workflow that still gets in the way.

The planned 1.0 time-lost summary compares each leg against the best split as one of its columns; this item is the dedicated view built on top of it: every leg's gap to the fastest recorded split across the field, side by side rather than inside the summary. The reference comes from the imported results, not an estimate of the fastest possible route.

Review more than two permitted routes together, for example at a club analysis evening. Build on the two-runner comparison rather than adding a separate workflow.

Make it easier to review analyses from several athletes, with their permission. Access controls and privacy come first, especially for juniors; this isn't a plan to make athletes' training public.

Work with a map and track without uploading either. This would be a separate mode with clear limits on saving, syncing and services that need a connection. Dibber's current browser app is not local-only.

Review a route against the shape of the terrain. The question is whether it helps explain route choices enough to justify the extra complexity.

Browse analyses that their owners have explicitly chosen to publish. This would build on share links' public pages, with attention to map rights, privacy and course embargoes. Unlisted analyses wouldn't appear automatically.

Explore analysis for events where runners choose the control order, and ways to group stages or days. Rogaining and mountain marathons may need different comparisons from a fixed-order course.

Consider shared administration or billing if clubs need it. There are no committed features, prices or launch dates for this.

I built an early version of this and put it aside because it was too much to maintain well on my own. I would revisit a specific need, such as a coaching group, rather than promise a full social platform.

Explore optional AI-assisted notes grounded in data you choose to provide. They would need to distinguish observations from guesses. This isn't a planned feature yet.

Use your track and the map's own text to suggest starting tie points and make matching your map to the background map easier. You always review an editable draft first — suggested points you can move or remove, then confirm or discard them; nothing is applied silently. Confirming uses the suggestion allowance: 1 accepted placement per calendar month per account on Free, unlimited accepted placements on Plus, and 1 accepted placement per guest session for a guest session. Suggested placements consume no map-text recognition credits, and Manual alignment is unlimited.

Send a race analysis to a coach or clubmate without making them create an account. Links are unlisted by default, with an explicit choice to make a page public and indexable. An unlisted link can still be forwarded: you'll need permission to share the map and must follow the organiser's course-release rules.

Paste a results list and Dibber reads the times into an editable review table you can correct row by row, then places your controls along the track. The times are stored as the race's official results times, and they drive the analysis where a control has one — each control's time is labelled official or track-derived.

Add a cause to each leg from a fixed list: route choice, lost map contact, pace, technique or other. You enter and edit every label yourself; the app never infers causes from GPS.

On the home page, pick a year and see how often each cause appears across your races and how much time is attributed to it, with tagged and untagged legs kept apart and unattributed loss shown separately. Every time-loss total shows the calculation basis behind it.

Export supported leg and split data for a spreadsheet or another tool. PDF and PNG exports already cover printing.

Choose a light or dark theme, or follow your device setting. Save reusable project settings as templates. Both are available on Free. Exports can follow the theme or use an explicit light/dark choice.

Add points between existing route points without redrawing a leg. Adjust your base pace to preview estimated times, and reuse your last export preset.

Guides for imports, map alignment, route editing, analysis and exports, with help links alongside the relevant tools. Browse the help centre.

Live tracking: Dibber focuses on reviewing a race afterwards, not tracking it as it happens.

Native iOS and Android apps: the browser app is the focus. Supported browsers already let you install it to your home screen.

Direct Garmin auto-upload: access to Garmin's developer programme isn't available to this project. For now, use exported FIT, GPX or TCX files. Garmin import options.

Federation systems and contracts: results publishing, procurement and federation-wide support are outside what I can offer as a solo developer.