What's next for Kwest

Kwest ships as a working, deployable app today — plan generation, guided sessions, history/stats, and Bluetooth cardio integration all run in production. Here's what we're prioritizing next.

In progress

• Rest-timer settings, per set and per exercise. The core rest-timer countdown (with pause/skip) already runs on every set and exercise transition. Next up is a settings panel to tune rest-between-sets separately from rest-between-exercises, instead of one shared default.
• Swipe navigation in Session. Moving between exercises during a guided workout currently uses on-screen controls; touch-swipe gesture navigation is next so it feels natural one-handed, mid-set, with a plate in the other hand.
• Broader Bluetooth device validation. Kwest's FTMS and iFit parsers are built directly against the published spec (and, for iFit, reverse-engineered protocol detail) and pass their unit tests — the next step is validating against a wider range of real bikes, rowers, and treadmills in the wild.

Also on the list

• Expanding OAuth coverage and polishing the sign-in flow further.
• Growing the admin-curated exercise catalog — more movements, more demonstration media, more equipment coverage.
• Deeper trend analysis in History — more ways to slice volume, frequency, and per-exercise progress over longer windows.

What's already solid

To be clear about what's not on a "someday" list — plan generation (goal/level/BMI/equipment-aware), the full guided-session flow, server-side history and stats, FTMS and iFit live metrics, subscriptions, and admin tooling are all built and running today. The roadmap above is about extending an app that already works, not filling in a skeleton.