Native packaging is closer to Play testing
Protocol tightened the native packaging path so the Android app can carry the same training experience into Play testing with fewer platform surprises.
Shipped
- Strengthened the Capacitor build path that packages Protocol Training for Android.
- Kept the native app pointed at the hosted services it needs while preserving local-first workout execution.
- Updated Play Store-facing visual assets and app icon treatment.
- Improved native-safe startup, account, and recovery behavior.
- Kept Android beta packaging aligned with the public beta product model.
Why
A native app is not useful if it drifts away from the product people already use.
Protocol's Android path is built around the same Training app: the same routine compiler, the same workout player, the same local-first bias. The packaging work is about making that experience installable and testable without creating a separate native product with separate rules.
This release moves that path closer to Play testing. The visible changes are simple: cleaner app identity, better mobile launch behavior, and fewer confusing account or access states. The important product constraint stays the same: training should continue to feel like Protocol, whether it opens in the browser or inside the native shell.
This is still beta packaging work, not a broad public store launch announcement.
Notes
- Android testing readiness is separate from public Play Store availability.
- The app remains local-first for workout execution.
- Platform packaging work should not change routine behavior by itself.
Next
- Rebuild the native package for the current release.
- Continue testing install, launch, routine setup, workout execution, account, and recovery flows before wider distribution.