Protocol has a native app path
Protocol now has the native app foundation needed for Android testing and future store distribution, without changing the local-first training model.
Shipped
- Added a Capacitor native shell for Protocol Training.
- Added Android and iOS project foundations around the same training app instead of creating a separate native product.
- Added the routing and hosted-page split needed for mobile-safe workout, timer, day, and summary paths.
- Added native-aware API boundaries so the app can talk to the right hosted services without weakening local-first workout execution.
- Prepared the Android app bundle path for testing, while keeping store availability separate from this update.
Why
Protocol has been a web app first, but training does not always happen in a desktop browser.
The native app work matters because it moves Protocol closer to where workouts actually happen: a phone in the gym, between sets, with spotty signal and a short attention span. That does not mean rebuilding the product as a different app. The important part is carrying the same routine compiler, workout player, and local-first behavior into a native shell that can pass mobile platform checks.
There is boring work behind that: app icons, splash screens, Android and iOS projects, native routing, hosted route seams, API origin handling, haptics, and app-bundle packaging. None of it should be visible as complexity to the lifter. It should just make the app more realistic to install, test, and eventually distribute.
This is not a store launch announcement. It is the path that makes proper Android testing and store readiness possible.
Notes
- The training model is still local-first.
- The native shell does not turn Protocol into a medical, sensor, or coaching app.
- Android testing readiness is not the same as public store availability.
- iOS foundation work exists, but this update does not announce an App Store release.
Next
- Keep testing the native install path on real devices.
- Keep mobile route behavior aligned with the web app so training state does not split by platform.
- Move toward store distribution only when the install, launch, workout, account, and subscription paths are clean enough.