Skip to content

Open-source gym & body-weight tracker, now in the App Store (iPhone + Apple Watch) and as an Android APK. Plan routines, log workouts, see which muscles are trained, import from Strong/Hevy/FitNotes. Self-host it or use it on the phone alone.

Roadmap: a release every two weeks — fifteen dated milestones from v1.3.8 (promised items, 2026-09-27) through v1.4.7 (2027-04-18), v1.4.0 is the database

Duarte Santosa68a88d2da04
diff --git a/README.md b/README.md
index c5fad884a..ae209c69a 100644
--- a/README.md
+++ b/README.md
@@ -214,14 +214,13 @@ host side of that volume, not the variable.
## Roadmap
-The plan lives in [ROADMAP.md](ROADMAP.md) (the
-[GitHub milestones](https://github.com/DuarteSantos8/openGym/milestones) hold the issues): v1.3.8 the
-promised small items and editing finished workouts, v1.3.9 programmes and progression (session queue,
-multi-week programmes, phases, the progression engine), **v1.4.0 the foundation — storage moves to a
-database and search is rebuilt, the one compatibility break**, v1.4.1 accounts (password and OIDC login,
-trainer role, MCP write), v1.4.2 the iOS app and the mobile items (HealthKit, Health Connect, timer in the
-notification bar, widgets), v1.4.3 what those unlock (pictures for custom exercises, catalogue work, skins,
-social). Ideas and pull requests welcome.
+The plan lives in [ROADMAP.md](ROADMAP.md), and the
+[GitHub milestones](https://github.com/DuarteSantos8/openGym/milestones) hold the issues. **A release every
+two weeks**, each one small and themed: the promised items, editing finished workouts, the session queue,
+programmes and phases, the progression engine, cardio — then **v1.4.0, the foundation: storage moves to a
+database and search is rebuilt, the one compatibility break** — then accounts (password and OIDC login,
+trainer role, MCP write), the iOS app, the Android and health items, and what all of that unlocks
+(pictures for custom exercises, catalogue work, skins, social). Ideas and pull requests welcome.
## Tech
diff --git a/ROADMAP.md b/ROADMAP.md
index 2b13a2488..0c04fe3e7 100644
--- a/ROADMAP.md
+++ b/ROADMAP.md
@@ -1,18 +1,19 @@
# Roadmap
Where openGym is going, in the order it is likely to land. Each block is a GitHub milestone; the
-issues and pull requests attached to it are the plan, this file is the readable summary. The
-dates are the order, not a promise: a one-maintainer self-hosted project ships a version when the
-branch has been used in a real gym for a while. Blocks are deliberately over-full — whatever is not
-done when a version ships rolls into the next one. Version numbers follow the release rule, not the
-size of the change: the next release is the last published one plus one patch (1.3.1 → 1.3.2), and a
-minor bump is reserved for something that breaks compatibility.
+issues and pull requests attached to it are the plan, this file is the readable summary.
+
+**A release every two weeks, on a Sunday.** Each one is small on purpose: a handful of issues, one
+theme, so a version is out before the branch has drifted and every fix reaches phones within a
+fortnight. Whatever is not merged and tested on gym-test by the Friday before rolls into the next
+block, the date does not move. Version numbers follow the release rule, not the size of the change:
+the next release is the last published one plus one patch (1.3.7 → 1.3.8), and a minor bump is
+reserved for something that breaks compatibility — that is v1.4.0, the database.
- Milestones: https://github.com/DuarteSantos8/openGym/milestones — every open issue sits in exactly one
-- Order: v1.3.8 the promised items and history editing → v1.3.9 programmes and progression → **v1.4.0 the
- foundation (database and search, the one compatibility break)** → v1.4.1 accounts → v1.4.2 the iOS app
- and mobile → v1.4.3 everything that those two unlock
-- "In review" means: on a branch and deployed to gym-test.duarte-santos.ch, waiting for a real session.
+- Tracks, in order: promised items → history editing → queue and programmes → the progression
+ engine → cardio → **the foundation (database, then search)** → accounts → the iOS app → Android
+ and health → exercises → looks and social
---
@@ -71,132 +72,139 @@ the phone, nginx resolver, custom-exercise equipment, per-side data, warm-up res
QA sweep of every screen. Left over: routine reordering (#142), the Smith-bar "no bar" option
(#138), two decimals (#139), delete user in the admin (#107).
-## v1.3.8 — Promised & history (October 2026)
-
-**Theme: pay the debts before building anything new.** Everything here was either promised on the
-tracker with a version number, or is the single most requested thing (editing a finished workout).
-Small, and every item is its own commit.
+## v1.3.8 — Promised items (2026-09-27)
- Reorder routines in Plan; the Start sheet follows that order (#142)
- "No bar" per exercise, so Smith-machine lifts calculate plates and drop sets from 0 (#138)
- Two decimals on per-side weights, as a display toggle (#139)
- Delete a user from the admin dashboard: credentials, state file, subscriptions, Coach data (#107)
+- Custom-exercise muscle order is fixed, not click order; the import fallback classifies "wrist
+ curl", "row … neutral grip" and Romanian deadlifts correctly (Discord)
+- The small open pull requests: unknown-path redirect (#185), manifest behind an auth proxy (#184),
+ standard ß (#190), distance in feet and the distance mode (#177, #178)
+
+## v1.3.9 — Editing history (2026-10-11)
+
- **Edit a finished workout** — date, start time, duration, name, sets, weights, add or remove an
exercise; progression and 1RM history re-read the corrected session (#143; GitLab !127 and !139
- as reference, Discord "edit finished workouts", "edit past workouts time", "change the date")
+ as reference; Discord "edit finished workouts", "edit past workouts time", "change the date")
- Save a logged workout as a routine, repeat a past workout from History, undo finish (#111, #58,
- GitLab !130, Discord "Historic tab")
-- Relabel an "Unknown" exercise after an import without losing its sets (Discord)
-- Copy a workout as text for sharing or pasting into a chat (Discord "Improvement ideas")
-- Custom-exercise muscle order is fixed, not click order (Discord); the import fallback classifies
- "wrist curl", "row … neutral grip" and Romanian deadlifts correctly (Discord, `bpFromName`)
-- Auto-backup keeps the last N files instead of one per workout (#161, first half)
-- A "next step" hotkey that does not depend on focus, for a big button on a Pi (#133)
-- The small open pull requests: the unknown-path redirect (#185), the manifest behind an auth
- proxy (#184), standard ß (#190), distance in feet and the distance mode (#177, #178), body
- measurements (#82), extra passkeys and the device link (#95)
-
-## v1.3.9 — Programmes & progression (November 2026)
-
-**Theme: training structure beyond one weekly template.** The contributor work is already open;
-the job here is one model, then one merge at a time, each rebased and tested on gym-test.
+ GitLab !130; Discord "Historic tab")
+- Relabel an "Unknown" exercise after an import without losing its sets; copy a workout as text
+ (Discord)
+- Auto-backup keeps the last N files (#161, first half); a "next step" hotkey independent of focus
+ (#133); body measurements (PR #82), extra passkeys and the device link (PR #95)
+
+## v1.3.10 — Session queue & rotation (2026-10-25)
- A free-running session queue beside the fixed week — the next session is the next undone one,
- whatever the weekday — with an in-app editor and automatic refill (#158, #69, PR #167 and the
- editor on top of it; Discord "not forced into a weekly plan", "major good ideas" 1)
+ whatever the weekday — with an in-app editor and automatic refill (#158, #69; PR #167 and the
+ editor on top of it; Discord "not forced into a weekly plan")
+- Swipe between exercise cards during a workout (#113, GitLab !114)
+- Drag-and-drop exercise order that survives touch (#114 — the first version came out again on
+ 2026-09-07); the Start/Resume button as "next" during a workout (Discord)
+
+## v1.3.11 — Programmes & phases (2026-11-08)
+
- Programmes: routines grouped into a named block over weeks, with deload and rest weeks, several
- per profile (#159, GitLab !98, Discord "Programme mode", "folders")
+ per profile (#159, GitLab !98; Discord "Programme mode", "folders", "major good ideas" 1)
- Session phases — mobility / work / accessory / cooldown — with completion-only exercises for
stretching that stay out of volume and PRs (#57, #140; Discord "non-typed exercises")
-- The progression engine: rep and set ranges per set, a universal AMRAP / "to failure" flag, load as
- %1RM or auto with a stored training max, target RPE/RIR, triple and wave progression (#154, #153,
- #179, #186, #70, PRs #168 and #181; Discord "Sets to Failure", "More types of sets")
-- Multi-formula 1RM (#155), a warm-up generator that picks the ramp from load and lift (#156),
- assisted exercises as negative added weight (#176)
-- Exercise alternatives per routine slot, and Replace in the routine editor (#110, Discord)
+
+## v1.3.12 — Progression engine I (2026-11-22)
+
+- A universal AMRAP / "to failure" flag and rep or set ranges per set (#154; Discord "Sets to
+ Failure", "More types of sets")
+- Triple progression, reps → sets → load (#179, #186; PR #181)
+- Multi-formula 1RM with Epley as the default shown (#155); assisted exercises as negative added
+ weight (#176)
+
+## v1.3.13 — Progression engine II (2026-12-06)
+
+- Load as %1RM or auto with a stored training max, target RPE/RIR (#153)
+- Wave / percentage progression, 5/3/1 style (#70; PR #168)
+- A warm-up generator that picks the ramp from load and lift (#156)
+- Periodisation extras on top: mesocycle blocks, auto-regulation on RPE (#120)
+
+## v1.3.14 — Cardio, alternatives, groups (2026-12-20)
+
- Cardio: incline and intervals (rounds × work/rest), interval programmes such as C25k, rucking as
- distance + pace + load (#132, #169; Discord "incline treadmill", "cardio programs", "rucking");
- complexes and interval groups beside supersets (Discord)
-- Swipe between exercise cards during a workout (#113, GitLab !114), drag-and-drop exercise order
- that survives touch (#114 — the first version came out again on 2026-09-07), the Start/Resume
- button as "next" during a workout (Discord)
-- Periodisation extras once the engine is in: mesocycle blocks, auto-regulation on RPE (#120)
-
-## v1.4.0 — Foundation: database & search (December 2026 – January 2027)
-
-**Theme: change the floor once.** Storage moves from one JSON file per profile to a database, and
-search is rebuilt over the catalogue, custom exercises and history. This is the compatibility break
-the minor bump is reserved for, so it carries nothing that does not need it. The state file stays
-the import/export and backup format; the revision/merge contract from v1.3.6 stays the client
-contract. The database is what makes several writers on one profile (a trainer, the MCP server, a
-second app), per-location histories, shared exercises and the iOS sync honest.
-
-- Database: tables for workouts, sets, routines, weigh-ins, custom exercises, favourites,
- credentials, push subscriptions and Coach data; idempotent migration on first start; the old files
- kept until the admin removes them; which database is decided in the issue (embedded by default so
- `docker compose up` stays one line; a server database as an option — Discord "Postgres/SQLite")
-- Search: one index over catalogue names in every language, import aliases and custom exercises;
- typo tolerance (GitLab !122) and a live result count (!31); filters that compose; history search
- for the Coach and MCP; built once per catalogue version, not per keystroke
+ distance + pace + load (#132, #169; Discord "incline treadmill", "cardio programs", "rucking")
+- Exercise alternatives per routine slot, and Replace in the routine editor (#110; Discord)
+- Complexes and interval groups beside supersets (Discord)
+
+## v1.4.0 — Foundation: database (2027-01-10)
+
+**The one compatibility break.** Storage moves from one JSON file per profile to a database (#191):
+tables for workouts, sets, routines, weigh-ins, custom exercises, favourites, credentials, push
+subscriptions and Coach data; an idempotent migration on first start; the old files kept until the
+admin removes them. The state file stays the import/export and backup format, and the revision/merge
+contract from v1.3.6 stays the client contract. Which database is decided in the issue — embedded by
+default so `docker compose up` stays one line, a server database as an option (Discord
+"Postgres/SQLite"). Nothing else rides on this release; it gets the three-week slot over the holidays.
+
+## v1.4.1 — Foundation: search (2027-01-24)
+
+- Search rebuilt over catalogue names in every language, import aliases, custom exercises and
+ history: typo tolerance (GitLab !122), a live result count (!31), filters that compose, built once
+ per catalogue version (#192)
- Shared custom exercises between accounts on one instance (#151)
-- Admin: per-user export, invite management, audit log filters
- "Different gyms": a location on a logged set, separate histories and PRs per location, bodyweight
- shared (Discord "How to deal with different gyms" — designed in that thread, built here)
-
-## v1.4.1 — Accounts & integrations (February 2027)
+ shared (Discord "How to deal with different gyms")
+- Admin: per-user export, invite management, audit log filters
-**Theme: who may sign in, and what else may read or write your data.** Everything here writes to
-credentials or to a profile from outside the app, so it lands on the new database, not before it.
+## v1.4.2 — Accounts: password & OIDC (2027-02-07)
- Optional username + password login next to passkeys (#118; Discord "Basic login", the
password-manager thread)
- OIDC login for PocketID / Authelia-style setups (#130, #72; GitLab !132 is the candidate)
+
+## v1.4.3 — Trainer & MCP write (2027-02-21)
+
- Personal-trainer role: invite students by code, open a student read-only, write their plan (#119,
GitLab !79; Discord "Trainer & Student Management")
-- MCP write tools — routines, log corrections, equipment — in pieces (#116), and remote MCP over
- OAuth for hosted AI clients (GitLab !88)
+- MCP write tools — routines, log corrections, equipment — in pieces (#116); remote MCP over OAuth
+ for hosted AI clients (GitLab !88)
- Switching kg ↔ lb converts stored values instead of relabelling them (#22)
-## v1.4.2 — iOS app & mobile (March 2027)
+## v1.4.4 — iOS app (2027-03-07)
-**Theme: the same app on both phones, talking to the same server.** The Capacitor iOS target has
-existed since the Android build; what was missing was an Apple developer account and a reason. The
-database and the sync contract are the reason: an App Store app that reads the profile through the
-same API as the web app, and the health integrations that a Home Screen web app cannot do.
+- App Store / TestFlight build of the existing Capacitor target, HealthKit weight and workout
+ export, the Home Screen icon and timer-sound issues gone for good (#90; Discord "Google Health")
+- Apple Watch rest timer later, once the app is in the store
-- iOS: App Store / TestFlight build, HealthKit weight and workout export, the Home Screen icon and
- timer sound issues gone for good; Apple Watch rest timer later (#90; Discord "Google Health")
-- Android: Health Connect for weight and sessions (Discord "Use health connect"), the rest timer as
- an ongoing notification on the lock screen (#122), a home-screen widget (#125), APK back under
- 10 MB with ABI filters (#136), the auto-backup directory picker (#161, second half)
-- Withings and other scales (#127)
-- Media for the routine's exercises cached on the phone, so a session works with no signal (#123,
- Discord "Download all videos")
-- Firefox-on-Windows QR and third-party passkey providers stay documented, not fixed here — they
- are platform behaviour (#103, #101)
+## v1.4.5 — Android & health (2027-03-21)
-## v1.4.3 — Exercises & more (April 2027)
+- Health Connect for weight and sessions (Discord "Use health connect"); Withings and other scales
+ (#127)
+- The rest timer as an ongoing notification on the lock screen (#122); a home-screen widget (#125)
+- APK back under 10 MB with ABI filters (#136); the auto-backup directory picker (#161, second half)
+- Media for the routine's exercises cached on the phone, so a session works with no signal (#123;
+ Discord "Download all videos")
+- Firefox-on-Windows QR and third-party passkey providers stay documented, not fixed — platform
+ behaviour (#103, #101)
-**Theme: what the foundation and the two apps unlock.** Ideas, not commitments; whatever is
-wanted most when v1.4.2 ships goes first.
+## v1.4.6 — Exercises & catalogue (2027-04-04)
- Pictures for custom exercises: pick from the catalogue, then upload; a video URL per exercise
(#126, #170; Discord "custom images/GIFs", "upload videos")
-- Catalogue: bench as equipment with flat / adjustable, TRX / suspension equipment, lats and the
- three delts as their own categories, exercises that should not carry weight, more routine icons
- (#132, #188; Discord)
+- Catalogue: bench as equipment with flat / adjustable, TRX / suspension, lats and the three delts
+ as their own categories, exercises that should not carry weight, more routine icons (#132, #188;
+ Discord)
- Choose what the "last time" line shows on the logger (#173); one progress line per set number
(#145); custom heatmap targets per muscle; a shareable image after a workout (Discord)
+
+## v1.4.7 — Looks, social, plugins (2027-04-18)
+
- Skins alongside the accent colour, backgrounds as part of a skin, a big-screen layout (#129,
#134, #135)
-- Social: friends, progress and plan sharing (PR #180); a plugin surface for integrations
- (Discord "plugin system")
+- Social: friends, progress and plan sharing (PR #180); a plugin surface for integrations (Discord)
- Native NixOS module (GitLab !83) and Azure deployment (!35) only if someone maintains them;
Arabic and right-to-left (GitLab !36) once rebased
## How things move
-An issue sits in exactly one milestone; whatever is not done when that version ships rolls into the
-next one. Contributor pull requests from returning contributors get their pipeline started here
+An issue sits in exactly one milestone; a milestone is a Sunday, and whatever is not merged and
+tested on gym-test by the Friday before rolls into the next one — the date stays. Contributor pull requests from returning contributors get their pipeline started here
automatically; a first PR is started by hand after a look at the diff. Anything in review is on gym-test.duarte-santos.ch. Releases
bundle whatever has passed that test, with a changelog section per contributor.