Roadmap
What ships and in which order. A phase is a layer of the product (architecture); a release is a set of features inside a phase that makes sense together, cut when it is ready, not on a date.
Proposal. The grouping below is a draft for the maintainer to approve in #229. Version numbers and release names are not final, and the GitHub milestones still follow the phases until it is decided. The current version is the latest tag on the Releases page.
Phase 1 · Guest app
Everything on the phone, no account. Phase 1 is done when the app is complete on both platforms: 1.0.
| Release | Theme | Issues |
|---|---|---|
| 0.6 | Easier to read and use | #222 smaller Home cards, #223 exercise details in the session recap, #221 back from devices, #220 a clearer pause button |
| 0.7 | Reuse and share workouts | #224 a workout from any session, #152 details before importing, #37 and #38 swap an exercise for a variation |
| 0.8 | Training plans | #17 follow a plan |
| 0.9 | Beyond the app | #22 FIT export, #23 Apple Health and Health Connect, #177 app icon, #24 TestFlight |
| 1.0 | Phase 1 complete | Whatever remains, then the stores |
Phase 2 · Treadmill
Runs alongside phase 1, because the treadmill link was the riskiest piece. Releases are cut with the phase 1 release they fall in.
| Theme | Issues |
|---|---|
| Live and the player work as one | #225 how much of the player Live shares (ADR 0018), #14 choose what a device measures |
Phase 3 · Accounts and sync
| Theme | Issues |
|---|---|
| A server to host | #28 hosting provider, #27 catalog updates on launch |
| Accounts | #25 accounts and sync between phones, #26 admin menu |
Phase 4 · Website
#29 run the shared engine in the browser with Kotlin/JS, then plan, review and run guided sessions.
Phase 5 · Sharing and coaching
Library sync or copy, coach links and comments. Not broken into issues yet.
Later
Wanted, not planned: #30 control the treadmill, #31 heart rate straps, #32 user-created exercises, #33 progression rules, #75 guided building of a long run, #124 Poulpy's coaching style, #228 APIs and an MCP server.
Not tied to a release
Documentation work (#226 diagrams, #227 readability) and #229, which defines how releases are planned, go in whichever release is open.