Beta access is clearer
Protocol now explains beta access more directly, keeps the core training flow available during the public beta, and makes native beta behavior easier to understand.
Shipped
- Updated the public beta experience so the app is clearer about what is available now and what is still reserved for later.
- Made the pricing and upgrade surfaces match the current beta access model instead of implying a paid checkout is always the next step.
- Improved account and subscription status copy so access state is easier to read.
- Added Android beta handling that keeps the native app path aligned with the same account-backed access model.
- Cleaned up old Pro launch language that no longer matched the current beta.
Why
Beta software should not make people decode the business model before they train.
Protocol is still proving the core Training product: building routines, running workouts, reviewing history, and making progression understandable. During this phase, the app needs to be plain about the difference between the beta, future paid plans, and platform-specific native testing.
This pass removes ambiguity from the surfaces a user actually sees. If access is available in the beta, the app should say that. If a paid plan is not the current path, the app should not nudge someone toward stale checkout language. If someone is using the Android beta, the app should still explain account state in normal product terms.
The goal is simple: fewer surprises between opening Protocol, starting a routine, and understanding what account tier you are on.
Notes
- Public beta access does not mean every planned Pro feature is finished.
- Native beta access is still separate from a public store launch.
- Account-backed access remains the source of truth for status shown in the app.
Next
- Keep the beta copy aligned with what is actually available in the product.
- Keep upgrade and subscription surfaces boring, explicit, and easy to verify.