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: v1.4.3 in review, v1.4.4 programmes, v1.4.5 remote MCP and Google Play, an honest later list; README and docs FAQ follow

Duarte Santosa7cb10e5ad8d
diff --git a/README.md b/README.md
index 754ee5284..c5d1c7d89 100644
--- a/README.md
+++ b/README.md
@@ -285,18 +285,19 @@ The [documentation index](docs/README.md) sorts every guide by who it's for. The
## Roadmap
-A release roughly every two weeks, each small and themed. The full plan is in
-[ROADMAP.md](ROADMAP.md), and the issues sit in the
+A release roughly every one to two weeks, each one whatever has passed testing by then. The full
+plan is in [ROADMAP.md](ROADMAP.md), and the issues sit in the
[GitHub milestones](https://github.com/DuarteSantos8/openGym/milestones).
| Release | When | Theme |
|---|---|---|
| v1.4.0 | released Oct 2026 | A new exercise database with 5,632 exercises, plus two rounds of community work |
| v1.4.1 | released Oct 2026 | Bug fixes for v1.4.0 |
-| v1.4.2 | released Oct 2026 | The App Store, the Apple Watch, widgets, a Google Play build |
-| v1.4.3 | Oct 2026 | The gym reminder, health data read back, community features |
-| next | Nov 2026 to Apr 2027 | Programmes, the progression engine, cardio, sharing, accounts, Android and health, looks |
-| later | | Database storage |
+| v1.4.2 | released Oct 2026 | The App Store, the Apple Watch, widgets, three APK sizes |
+| v1.4.3 | in App Review | The community release: gym reminder, health data read back, watch upgrades, CSV export |
+| v1.4.4 | in progress | Programmes with %1RM and RPE targets, custom app icons, kg or lb per exercise, the Coach fix |
+| v1.4.5 | Nov 2026 | Remote MCP over HTTPS, Google Play, a gym reminder that also notices you leaving |
+| later | dates are guesses | Circuits and EMOM, a trainer role, OIDC, F-Droid, an on-device Coach, Strava and Garmin, database storage |
## Community
diff --git a/ROADMAP.md b/ROADMAP.md
index 0de6247d0..5bcf9129b 100644
--- a/ROADMAP.md
+++ b/ROADMAP.md
@@ -1,19 +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.
+Where openGym is going, in the order it is likely to land. The next two releases are planned in
+detail; everything after that is a list in rough order, and any date on it is a guess. The GitHub
+milestones and the issues in them are the working 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 a step as big as the new exercise database (v1.4.0).
+**A release roughly every one to two weeks.** Each one bundles whatever has been merged and tested
+on gym-test by then, so a fix reaches phones quickly and a branch never drifts for a month. Store
+builds add a few days of App Review on top, which is why a version can be "done" before it is out.
+Version numbers follow the release rule, not the size of the change: the next release is the last
+published one plus one patch (1.4.2 → 1.4.3), and a minor bump is saved for a step as big as the
+new exercise database (v1.4.0).
-- Milestones: https://github.com/DuarteSantos8/openGym/milestones (every open issue sits in exactly one)
-- Tracks, in order: the App Store (v1.4.2) → community features (v1.4.3) → programmes →
- Google Play with the progression engine → cardio → search → accounts → trainer → wearables → looks
- and social, with database storage after that
+- Milestones: https://github.com/DuarteSantos8/openGym/milestones
+- Next, in order: the community release (v1.4.3, in App Review) → programmes and the Coach fix
+ (v1.4.4) → remote MCP and Google Play (v1.4.5) → the list after that
---
@@ -162,71 +162,70 @@ The animations come back as WebP, and the Android update check reads GitHub.
- Your bars, rest between warm-ups and between sides, backups for an exercise, the boot screen,
five reported security holes closed
-## v1.4.3: Gym reminder, health data & community features (2026-11-01)
-
-- Gym reminder: a nudge when you walk into your gym (#614)
-- Heart rate per set and weigh-ins read back from Health Connect and Apple Health, so Garmin,
- Fitbit, Samsung, Polar and friends show up via the phone (#544)
-- Nicer PDFs with the logo, and a performance report for a week, a month or three
-- Less battery: the rest timer stops keeping the phone awake, long histories load in pieces
-- CSV export, and importing GymMane's CSV (#647)
-- Account recovery (#584), the rotation fix (#536), community PRs and bug fixes (#620, #631)
-
-## v1.4.4: Programmes & phases (2026-11-15)
-
-- Programmes: routines grouped into a named block over weeks, with deload and rest weeks, several
- per profile (#159; Discord "Programme mode", "folders")
-- Session phases (mobility / work / accessory / cooldown) with completion-only exercises for
- stretching that stay out of volume and PRs (#57, #140)
-- Alternatives per routine slot, for when the machine is taken or you're at another gym (#649)
-- Body composition in measurements: fat %, muscle mass, water and friends (#648)
-
-## v1.4.5: Google Play & progression engine I (2026-11-29)
-
-- openGym on Google Play by then at the latest; Google wants a closed test with 12 testers for
- 14 days first, so it can land earlier
-- Android home-screen widget and an ongoing workout notification (#125)
-- Rep or set ranges per set and AMRAP targets beyond the "to failure" flag (#154)
-- Assisted exercises as negative added weight (#176)
-
-## v1.4.6: Progression engine II (2026-12-13)
-
-- 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)
-- Mesocycle blocks and auto-regulation on RPE (#120)
-
-## v1.4.7: Cardio, alternatives, groups (2026-12-27)
-
-- Cardio: intervals, interval programmes such as C25k, rucking, distance for cardio (#132, #169, #177)
-- Complexes and interval groups beside supersets (Discord)
-
-## v1.4.8: Search & catalogue (2027-01-10)
-
-- Searching your own history, import aliases by name, more icons (#188)
-- Your own photos and videos on built-in exercises (#534)
-- Shared custom exercises between accounts on one instance (#151)
-- "Different gyms": separate histories and PRs per location (Discord)
-
-## v1.4.9: Accounts: password & OIDC (2027-01-24)
-
-- OIDC login for PocketID / Authelia-style setups (#130, #72); password login is already there
- behind `PASSWORD_LOGIN` (#118)
-
-## v1.4.10: Trainer & MCP write (2027-02-07)
-
-- Personal-trainer role: invite students, open a student read-only, write their plan (#119)
-- MCP write tools (routines, log corrections, equipment) in pieces (#116)
-
-## v1.4.11: Wearables: Wear OS, Garmin & more (2027-02-21)
-
-- A Wear OS watch app, then a Garmin Connect IQ app on the watch itself
-- Real sets and calories written to Health Connect; Withings and other scales via the hubs (#127)
-
-## v1.4.12: Looks, social, plugins (2027-03-07)
-
-- Skins alongside the accent colour, a big-screen layout (#129, #134, #135)
-- Social: friends, progress and plan sharing (PR #509); a plugin surface for integrations
+## v1.4.3: The community release (in App Review, out around 2026-10-27)
+
+Most of it was asked for on GitHub and Discord or sent in as a pull request. The full list is in
+the changelog; the headlines:
+
+- openGym starts again on iOS 15.5 to 16.3, where 1.4.2 sat on the splash screen forever
+- Gym reminder: a nudge when you walk into your gym, gyms stay on the phone (#614)
+- A tiny muscle map on every routine and in the workout (#670); volume while you lift (#774)
+- CSV export and GymMane import (#647); keep an exercise you added mid-workout (#592)
+- Backups per routine slot for when the machine is taken (#649), weight stacks for machines with
+ odd steps (#688), rest after a single set (#609), rest days in the rotation (#536)
+- Heart rate and weigh-ins read back from Apple Health and Health Connect (#544, #127)
+- The Apple Watch learns RPE, a countdown, Water Lock and proper Discard (#776, #783, #789 to
+ #791); next exercise and Skip rest on the Lock Screen
+- The Coach answers questions and plans into the rotation (#778, #779); Swedish, and Spanish
+ from Spain (#786); the MCP server can log a workout (#739)
+
+## v1.4.4: Programmes (in progress, about two weeks after v1.4.3)
+
+- **Programmes**: routines grouped into a block over several weeks, with targets as %1RM or RPE
+ per week, deloads included (#159, #679)
+- The Coach works again with OpenAI-compatible endpoints that answered HTTP 400 (#804)
+- Your own app icon, on iPhone and Android
+- kg or lb per exercise, for the one dumbbell rack that lives in pounds (#657)
+- Body weight in pull-up and dip volume, as a switch, because it changes every number (#794)
+- The catalogue files each exercise under the muscle it is known for, so fatigue and balance shift
+ a little for everyone (#788, thanks @lodepav)
+- Timed sets that start themselves after the rest, and superset intervals (#626)
+- The Apple Watch redesign by @cubetes, one screen per pull request (Discussion #777)
+
+## v1.4.5: Remote MCP & Google Play (planned for the second half of November)
+
+- MCP over HTTPS: your AI client signs in through the app with OAuth, no extra service (#781)
+- Watch follow-ups for RPE, from what people say about the v1.4.3 watch
+- Change your display name in the app
+- The gym reminder learns two more tricks (#614): walk out of the gym with a workout still running
+ and it asks "Still training? Tap to finish", and an optional nudge a set time after your last
+ logged set to finish or discard, like the watch's idle check (#790). Same rules as the arrival
+ nudge: off by default, your gyms stay on the phone
+- **openGym on Google Play.** A new developer account needs a closed test with 12 testers for
+ 14 days first, so that test has to start around 2026-11-05 for a launch at the end of November.
+ Until then the signed APK on GitHub is the Android app.
+
+## After v1.4.5 (in rough order, dates are guesses)
+
+None of these has a version number yet. They get one when the work starts, and the order can change
+when the tracker or Discord says so.
+
+- **Circuits, AMRAP and EMOM** as one design instead of three features (#765, #725, Discussion #797)
+- **Personal-trainer role**: invite students, look at their training, write their plan (#119)
+- **Sign in with OIDC** (PocketID, Authelia and friends). PR #391 is the starting point, but it
+ needs splitting into pieces that can be reviewed (#130)
+- **F-Droid** (#325). The exercise animations are licensed, not free, so the first step is asking
+ F-Droid whether the 180 px media can ship with a NonFreeAssets label at all
+- **A free Coach on the phone itself**, with Apple Foundation Models on iOS and Gemini Nano on
+ Android, so no API key is needed
+- **Deeper Health Connect sync**: more history on the first read, real sets and calories written
+ back, scales via the hubs (#127)
+- **Strava and Garmin**: workouts out to Strava, Garmin through FIT files rather than a watch app
+- **Still on the list from older plans**: body composition in measurements (#648), session phases
+ (#57), rep ranges and AMRAP targets (#154), a warm-up generator (#156), cardio intervals,
+ searching your own history and your own photos on built-in exercises (#534), account recovery
+ (#584), the Android home-screen widget (#125), a Wear OS app, skins (#129) and social sharing
+- **openNutrition**, the sister app for food, once openGym's stores are settled
## Later: database storage
@@ -236,11 +235,13 @@ subscriptions and Coach data; an idempotent migration on first start; the old fi
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"). It gets a version number once the work starts, and nothing else rides on that release.
+"Postgres/SQLite"). It gets a version number once the work starts, and nothing else rides on that
+release.
## How things move
-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, and 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.
+An issue sits in at most one milestone. Whatever is not merged and tested on gym-test by release
+day rolls into the next one; the release does not wait for it. Pull requests from returning
+contributors get their pipeline started 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 thank-you per contributor in the changelog.
diff --git a/website/docs.html b/website/docs.html
index 59a23d9dc..7b9f1f44e 100644
--- a/website/docs.html
+++ b/website/docs.html
@@ -31,7 +31,7 @@
<!-- Umami web analytics for opengym.ch (self-hosted, cookieless). -->
<script defer src="https://stats.duarte-santos.ch/script.js" data-website-id="db36019e-50f4-453c-9c56-d0588aefe233"></script>
<script type="application/ld+json">
-{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Is openGym really free?", "acceptedAnswer": {"@type": "Answer", "text": "Yes — free as in cost and as in freedom (AGPL-3.0). No pro tier, no locked features, no ads, and the license keeps every fork open source too."}}, {"@type": "Question", "name": "Is openGym in the App Store and on Google Play?", "acceptedAnswer": {"@type": "Answer", "text": "The App Store: yes, since 23 October 2026, for iPhone and Apple Watch (https://apps.apple.com/app/id6822275400). Google Play follows once a new developer account has finished its closed test. On Android the signed APK is a direct download in the meantime."}}, {"@type": "Question", "name": "Should I pick the mobile app or self-host?", "acceptedAnswer": {"@type": "Answer", "text": "To simply track your training: the mobile app. For data on your own hardware, synced across devices, with profiles for the people you train with: self-host with Docker. The backup file migrates everything between the two, or pair the app to your server."}}, {"@type": "Question", "name": "What's on the openGym roadmap?", "acceptedAnswer": {"@type": "Answer", "text": "A small, themed release every two weeks: the gym reminder and health data read back from the phone (v1.4.3), then programmes and phases, Google Play with a new progression engine, cardio, better search, password and OIDC accounts, a trainer role, wearables, and database storage after that. The full plan is in ROADMAP.md on GitHub."}}, {"@type": "Question", "name": "Was openGym written with AI?", "acceptedAnswer": {"@type": "Answer", "text": "openGym is developed with Claude Code, Anthropic's coding agent; a large share of the code, tests and docs is drafted that way, and every change is reviewed, tested and released by the maintainer. The app itself calls no AI service unless an admin switches on the optional AI coach."}}, {"@type": "Question", "name": "Where does the exercise database come from?", "acceptedAnswer": {"@type": "Answer", "text": "The exercise text lives in openGym's own catalogue in the repository, open to fixes and translations by pull request; the oldest entries came from ExerciseDB under MIT. The pictures and animations are licensed from Gym visual for use in openGym only and ship with it at 180 px. Reusing them anywhere else needs your own licence from gymvisual.com."}}, {"@type": "Question", "name": "What does the AGPL license mean for me?", "acceptedAnswer": {"@type": "Answer", "text": "You can self-host, use, modify and share openGym freely. Only if you run a modified version as a network service must you offer that version's source under the same license. Using or self-hosting it unmodified obliges you to nothing."}}]}
+{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Is openGym really free?", "acceptedAnswer": {"@type": "Answer", "text": "Yes — free as in cost and as in freedom (AGPL-3.0). No pro tier, no locked features, no ads, and the license keeps every fork open source too."}}, {"@type": "Question", "name": "Is openGym in the App Store and on Google Play?", "acceptedAnswer": {"@type": "Answer", "text": "The App Store: yes, since 23 October 2026, for iPhone and Apple Watch (https://apps.apple.com/app/id6822275400). Google Play follows once a new developer account has finished its closed test. On Android the signed APK is a direct download in the meantime."}}, {"@type": "Question", "name": "Should I pick the mobile app or self-host?", "acceptedAnswer": {"@type": "Answer", "text": "To simply track your training: the mobile app. For data on your own hardware, synced across devices, with profiles for the people you train with: self-host with Docker. The backup file migrates everything between the two, or pair the app to your server."}}, {"@type": "Question", "name": "What's on the openGym roadmap?", "acceptedAnswer": {"@type": "Answer", "text": "A release roughly every one to two weeks. v1.4.3 (gym reminder, health data read back, watch upgrades) is in App Review, v1.4.4 brings programmes with %1RM and RPE targets and custom app icons, v1.4.5 remote MCP and Google Play. After that, in rough order: circuits and EMOM, a trainer role, OIDC sign-in, F-Droid, a free on-device Coach, Strava and Garmin, and database storage. The full plan is in ROADMAP.md on GitHub."}}, {"@type": "Question", "name": "Was openGym written with AI?", "acceptedAnswer": {"@type": "Answer", "text": "openGym is developed with Claude Code, Anthropic's coding agent; a large share of the code, tests and docs is drafted that way, and every change is reviewed, tested and released by the maintainer. The app itself calls no AI service unless an admin switches on the optional AI coach."}}, {"@type": "Question", "name": "Where does the exercise database come from?", "acceptedAnswer": {"@type": "Answer", "text": "The exercise text lives in openGym's own catalogue in the repository, open to fixes and translations by pull request; the oldest entries came from ExerciseDB under MIT. The pictures and animations are licensed from Gym visual for use in openGym only and ship with it at 180 px. Reusing them anywhere else needs your own licence from gymvisual.com."}}, {"@type": "Question", "name": "What does the AGPL license mean for me?", "acceptedAnswer": {"@type": "Answer", "text": "You can self-host, use, modify and share openGym freely. Only if you run a modified version as a network service must you offer that version's source under the same license. Using or self-hosting it unmodified obliges you to nothing."}}]}
</script>
</head>
<body class="topnav dock">
@@ -1123,11 +1123,13 @@ Leg Day,Leg Press,2026-08-21,200,1</code></pre>
migrates everything, or <a href="#mobile-server">pair the app to your server</a> and
keep using it.</p>
<h3>What's on the roadmap?</h3>
- <p>A small, themed release every two weeks. Next up: the gym reminder and heart rate and
- weigh-ins read back from Health Connect and Apple Health (v1.4.3), then programmes and
- phases, Google Play with a new progression engine (AMRAP, %1RM and 5/3/1-style waves),
- cardio, better search, password and OIDC accounts, a trainer role, wearables, and database
- storage after that. The full plan with dates is in
+ <p>A release roughly every one to two weeks. v1.4.3 (the gym reminder, heart rate and
+ weigh-ins read back from Apple Health and Health Connect, a smarter Apple Watch) is in App
+ Review. v1.4.4 brings programmes with %1RM and RPE targets, your own app icon and kg or lb
+ per exercise; v1.4.5 remote MCP over HTTPS and Google Play. After that, in rough order and
+ with dates that are honest guesses: circuits and EMOM, a trainer role, OIDC sign-in,
+ F-Droid, a free Coach that runs on the phone, Strava and Garmin, and database storage.
+ The full plan is in
<a href="https://github.com/DuarteSantos8/openGym/blob/main/ROADMAP.md" rel="noopener">ROADMAP.md</a>;
ideas and pull requests welcome.</p>
<h3>Was openGym written with AI?</h3>