The old login flow was corrupting the data layer
Typing usernames and passwords on a simulator was inconvenient enough that many users simply did not do it. Sessions often happened in guest mode, or the trainer logged in once and everyone effectively used that identity.
That meant the company was collecting activity but not reliably linking it to the actual athlete who produced it.
The right question was reliability, not novelty
Bluetooth and Wi-Fi were possible in theory, but they introduced too much variability across user devices. The better solution was a behavior people already understood: scan a QR code with the phone that already holds the user session.
The simulator rendered a temporary token, the mobile app scanned it, and the user instantly entered the simulator under the correct identity.
- Touchless login on the device
- Familiar phone-based behavior
- Stronger identity resolution
- Less friction than simulator-side typing
The mobile app became more than a companion
Once the identity problem was solved, the mobile app became the place where users could see the value of their training history over time. That made profile persistence meaningful rather than administrative.
The strength of that value showed up in behavior: users even asked to migrate older workouts into their profiles so they could keep the continuity of their progress.
The moment users ask to restore old sessions, you know the profile stopped being a login container and became a product asset.
Why this mattered strategically
The cleaner identity layer improved engagement, analytics accuracy, and the long-term usefulness of the global training dataset. Within days the app gathered its first meaningful wave of users, and over time the base grew into the tens of thousands.
By 2026, that data was already informing a new generation of product thinking around training quality, progression, redesign, and AI-driven user insight.