What the mobile apps are
The member and staff apps are the same web application wrapped with Capacitor and shipped as native builds. The app identifier is app.bliply.gym. Most product changes reach phones through the web layer without a store release; a new release is only needed when native code, plugins, permissions or app configuration change.
Build steps
- Pull the branch and install dependencies.
- Build the web bundle, then run a Capacitor sync so the native projects pick it up.
- Open the native project and archive (iOS) or build a signed app bundle (Android).
Capacitor regenerates some native files during sync. If a pull refuses to merge because a generated file would be overwritten, delete the local generated copy and pull again — do not commit it.
Versioning
Android rejects an upload whose versionCode has been used before: every upload needs a higher number, with versionName bumped for anything a human will read. iOS follows the same principle with build numbers. Bump the version in the tracked project files so the change travels with the branch and nobody has to make a conflicting local edit.
On iOS, avoid build scripts that modify the project during an archive — they can cancel the archive with no useful error.
Store submission
- iOS — archive, upload, then distribute through TestFlight for internal testing before release.
- Android — upload the app bundle to a Play Console track, complete the release notes, then roll out.
Things that only work on a real build
Push notification tokens, camera and QR scanning, the photo library picker and deep links cannot be verified in the browser preview. Anything touching those needs a fresh device build before it is called fixed.