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.
JavaScript apple-watchbodyweightdockerfitnessfitness-trackergymhealthiosmcpnodejspasskeysprogressive-web-applicationspwareactself-hostedself-hostingvitewebauthnweightliftingworkout-tracker
Docs: the Standard (180 px) and HD (360 px) APKs everywhere; the old one-APK-at-240 and CI-built-APK lines are gone
Duarte Santose2e86e8d6059
diff --git a/README.md b/README.mdindex 769f38b83..04a09b5f9 100644--- a/README.md+++ b/README.md@@ -190,8 +190,9 @@ The same codebase builds a standalone app with Capacitor: no account, no server,on the phone, with native reminders and a rest countdown in the notification shade.- **Android:** download the signed APK from the [latest release](https://github.com/DuarteSantos8/openGym/releases/latest)- or the [website](https://opengym.ch). Each build sits next to its `.sha256`, and- the app checks for updates itself. A Google Play version is on its way.+ or the [website](https://opengym.ch): Standard (`openGym-X.Y.Z.apk`, 180 px animations, about+ 315 MB) or HD (`openGym-HD-X.Y.Z.apk`, 360 px, about 760 MB). Each sits next to its `.sha256`,+ checks for updates itself and stays the kind you picked. A Google Play version is on its way.- **iPhone and Apple Watch:** the App Store app, with a public[TestFlight beta](https://testflight.apple.com/join/RKATb61k) until it is out. Or self-host andadd the PWA to your home screen from Safari.@@ -303,8 +304,8 @@ two weeks after it.GitHub is the home of the project. [gitlab.com/DuarteSantos8/opengym](https://gitlab.com/DuarteSantos8/opengym)is a mirror, updated by a GitHub Actions workflow on every push to `main` and every release tag. It-exists because its CI builds the release artifacts: the signed APK, the multi-arch images and the-SBOMs. Nothing is merged there by hand. In the changelog, `!NN` refers to a GitLab merge request+exists because its CI builds the multi-arch images and the SBOMs for its registry (the APKs are+built and signed on the release machine and attached to the GitHub release). Nothing is merged there by hand. In the changelog, `!NN` refers to a GitLab merge requestfrom the weeks in August and September 2026 when the project lived there.## How openGym is builtdiff --git a/docs/APP_STORES.md b/docs/APP_STORES.mdindex 3f1156b83..1bd5be06d 100644--- a/docs/APP_STORES.md+++ b/docs/APP_STORES.md@@ -27,7 +27,7 @@ ever sees the repo's 180 px media.it). The sharper qualities, 240 included, are on-demand **Play asset packs** (Play AssetDelivery), one per quality and figure like the iPhone's, each under Play's 1.5 GB per pack (a bigger one is split into parts),far under the 30 GB for all on-demand packs together. Google Play delivers them; the sideloaded- APK has none and keeps its 240 px.+ APKs have none and keep what they have built in (Standard 180 px, HD 360 px).- **App Store:** built with Xcode 26 (the `macos-26` runner). Privacy manifest(`ios/App/App/PrivacyInfo.xcprivacy`): no tracking, no data collected. No non-exemptencryption (`ITSAppUsesNonExemptEncryption = NO`, HTTPS only). The Coach asks before anything@@ -50,11 +50,13 @@ cd gym-app # the release checkout, at the release tagexport ANDROID_HOME=/opt/android-sdkK=/root/.config/opengymscripts/android/build-release.sh $K/opengym-release.keystore $K/keystore.pass $K/key.alias ~/release-# → openGym-X.Y.Z.apk (+ .sha256) for the GitHub release, openGym-X.Y.Z.aab for Google Play+# → openGym-X.Y.Z.apk + openGym-HD-X.Y.Z.apk (each + .sha256) for the GitHub release,+# openGym-X.Y.Z.aab for Google Play```-Each is built from its own phone build: the APK with the box-free 240 px animations built in-(`quality/240`), the bundle with 180 px (`quality/180`, like the App Store app) and an asset+Each is built from its own phone build: the **Standard** APK with the box-free 180 px animations+built in (`quality/180`, about 315 MB), the **HD** APK with 360 px (`quality/360`, about 760 MB;+`HD_PX=240` makes a lighter one, `HD_PX=0` none), the bundle with 180 px (`quality/180`, like the App Store app) and an assetpack for every quality above 180 that has a folder in `/mnt/backup-hdd/opengym-media/quality/`(`scripts/android/make-asset-packs.mjs`, the same drawings per pack as the iPhone's); the packmodules are generated into `frontend/android/` for the build and removed after, never committed.diff --git a/docs/MOBILE.md b/docs/MOBILE.mdindex cc161e7cf..880827f04 100644--- a/docs/MOBILE.md+++ b/docs/MOBILE.md@@ -1,7 +1,8 @@# The phone app (Android and iOS)**Just want the app?** Download the APK from the-[latest release](https://github.com/DuarteSantos8/openGym/releases/latest) and read+[latest release](https://github.com/DuarteSantos8/openGym/releases/latest) (`openGym-X.Y.Z.apk`,+or `openGym-HD-X.Y.Z.apk` for sharper animations at about twice the size) and read[how the phone app works](#how-the-phone-app-works) and[connecting it to your server](#connecting-the-app-to-your-own-server). On an iPhone, see[what's possible](#iphone--whats-actually-possible). Everything from [Prerequisites](#prerequisites)@@ -266,8 +267,9 @@ and **Delete**.its `assets/anim-packs.json` lists, and serves their files to the page at`https://localhost/_opengym_pack/<packId>/<drawing>.webp`, never a file path. The pack modulesare generated on the release machine by `scripts/android/make-asset-packs.mjs` and never- committed. The `sideload` flavour (the APK) answers "unavailable" and only ever has its- built-in animations (240 px).+ committed. The `sideload` flavour (the APKs) answers "unavailable" and only ever has its+ built-in animations: 180 px in the Standard APK, 360 px in the HD one. Each APK's updater+ stays with its own kind (`pickApk` in `lib/update.js`, told by `VITE_APK_VARIANT`).App Store Connect, once: the App Group `group.ch.opengym.app`; the bundle id`ch.opengym.app.AnimationPacksDownloader` (an app extension); the App Groups capability on@@ -323,32 +325,23 @@ The App Store app (public TestFlight beta: https://testflight.apple.com/join/RKAGoogle Play build come from the same code; how they are built and uploaded is in[APP_STORES.md](APP_STORES.md).-### Android — sideload the APK--The official signed APK is in four places, all the same file:--- **[opengym.ch](https://opengym.ch)** — the download page.-- **[GitLab's package registry](https://gitlab.com/DuarteSantos8/opengym/-/packages)** — every- build under `opengym-android/<version>/`, with a `.sha256` beside it. Direct link, no login:- `https://gitlab.com/api/v4/projects/85678327/packages/generic/opengym-android/<version>/openGym-<version>.apk`-- **[The GitHub release](https://github.com/DuarteSantos8/openGym/releases)** for that version,- with the APK and its `.sha256` attached as release assets.-- **[The GitLab release](https://gitlab.com/DuarteSantos8/opengym/-/releases)** on the mirror,- where the file is built; it links to the package registry above.--Android asks you to allow installs from the browser the first time — that's standard for any-app outside the Play Store. Check the `.sha256` if you got the file from anywhere else.--Both come out of CI: the `build:apk` job in [`.gitlab-ci.yml`](../.gitlab-ci.yml) runs-`npm run build:mobile` and `./gradlew assembleSideloadRelease`, then `zipalign`s and signs the result-with the release key. The job runs on every push to `main` too, so the newest unreleased-build is always one click away (signed with the same key, installs over a release):-`https://gitlab.com/DuarteSantos8/opengym/-/jobs/artifacts/main/browse?job=build:apk`-— a 30-day job artifact, not a package, and not what the in-app updater offers. The key lives in *protected* CI variables (`ANDROID_KEYSTORE_B64`,-`ANDROID_KEYSTORE_PASSWORD`, `ANDROID_KEY_ALIAS`), so it only exists on `main` and on `v*`-tags — a merge request from a fork can build an APK, but gets an unsigned one and never sees-the key. On a `v*` tag the signed APK is also pushed to the generic package registry, which is-what the release links to.+### Android: sideload the APK++Every release has two signed APKs on [the GitHub release](https://github.com/DuarteSantos8/openGym/releases),+each with its `.sha256` beside it, and [opengym.ch](https://opengym.ch) links to both:++- **`openGym-X.Y.Z.apk` (Standard):** the exercise animations built in at 180 px, about 315 MB.+- **`openGym-HD-X.Y.Z.apk` (HD):** the same app with 360 px animations, about 760 MB.++Same app id, same key: install one over the other and the data stays. The in-app updater keeps+each on its own kind. Android asks you to allow installs from the browser the first time; that is+standard for any app outside the Play Store. Check the `.sha256` if you got the file from anywhere+else.++Both are built and signed on the release machine with `scripts/android/build-release.sh`+([APP_STORES.md](APP_STORES.md)), not in CI: anything above 180 px may only exist inside an app+package (Gym visual licence), never in a CI artifact. The GitLab mirror's `build:apk` job only runs+by hand and builds a plain 180 px APK; its releases link to GitHub's.The release APK carries native code for ARM only (`arm64-v8a`, `armeabi-v7a`), which is everyphone; the x86 builds of the barcode scanner's library would add about 12 MB for emulators