Mobile Product · Fitness Technology
Turning a training methodology into a structured mobile product
A coaching platform moved from a web-based experience into a dedicated mobile product, without losing the training logic that made the methodology work.
Domain modelling
Mobile product UX
Architecture and migration
Coach and client workflows
Release management and QA
The challenge
StepUp already existed as a web-based experience built on a WordPress and REST architecture. Moving to a dedicated mobile product was not a porting exercise, because the value of the platform was not in its screens—it was in a coaching methodology that had never been fully expressed in software.
A training programme has real structure: weeks contain days, days contain exercises, exercises carry sets and repetitions, and some of those exercises are grouped into circuits whose order is part of the method. Flatten any of that and the product still functions while quietly ceasing to represent the training.
The approach
I started with the domain rather than the interface, modelling the programme structure explicitly—weeks, training days, exercises, sets, repetitions, circuits and their ordering—so that the coaching logic lived in the data rather than in the layout of a particular screen.
That decision paid for itself twice. It made the training experience faithful to the methodology, and it meant later expansion into other disciplines such as running and swimming was a question of new programme content rather than new product architecture.
What I delivered
A React Native application delivered through Expo covering the training experience itself, programme and progress views, onboarding, and the coach-to-client relationship: invitations, referral workflows and the connection between a coach and the people they train.
Alongside the product work, the practical delivery layer that decides whether a mobile application ships at all—build and version management, device permissions, TestFlight distribution, App Store preparation and release QA across devices and screen sizes.
Outcome
The training methodology became something the software represents rather than approximates, and coaches gained a structured way to build and assign programmes rather than describing them outside the product.
The migration also left the platform on an architecture where adding a new training discipline is a content and configuration exercise, which is a materially different position from where it started.
My contribution
- Translating training methodology into a data model
- Mobile product UX and onboarding
- Architecture and migration from the previous web stack
- React Native development
- Build, version and release management
- Pre-release QA across devices
Technology
- Expo
- React Native
- Firebase Authentication
- Cloud Firestore
- Cloud Functions
- iOS
- Android
- WordPress REST API
- TestFlight
A clear next step
Start with the decision in front of you.
Get preliminary direction first, or book a focused session when the question is ready.