A training app should earn trust before asking for data
Protocol lets a lifter start locally and see the training value before deciding whether account-based continuity is worth sharing more information.
The view
The first useful moment in a training app should be the workout, not an account form.
A lifter arriving with a routine already has work to do: set up the plan, understand today's targets, and see whether the app stays out of the way once training starts. Asking for more information before proving that value reverses the relationship.
Protocol Training lets people begin locally. An account becomes relevant when someone wants continuity beyond that local experience.
What trust looks like in practice
Trust grows when the product's behavior is legible. The routine stays usable. Completed and missed work remain visible. Export and restore choices are clear. Optional sign-in does not block the first session.
Measurement should follow the same standard. Product signals can show whether an entry point is confusing or whether a useful flow is being reached, but they do not justify collecting private training detail without a clear purpose.
The business consequence
Lower-friction entry may produce fewer early account records. It also gives each later account decision a better foundation: the person has seen what Protocol does and can decide whether continuity is worth it.
That is a slower-looking number and a more honest product relationship.
The test
If you leave a workout app during setup, what usually caused it: the account request, the amount of configuration, or uncertainty about what happens to your data?