Mobile Fitness App
Runs inside a phone frame — log a set, switch tabs, watch the progress rings respond. The touch patterns I hand off for React Native builds.
Self-initiated. Built to demonstrate an approach — no client, no brief, no results to report.
The problem
Mobile interfaces are usually handed over as static frames, which hides the two things that actually matter: what happens between screens, and whether a target is reachable with one thumb.
What I did
- Built it as working state rather than as frames, so the transitions and the feedback are part of the deliverable.
- Sized every interactive target for a thumb and kept the primary actions inside the lower reachable band.
- Kept the progress rings driven by the same state the log writes to, so the two cannot show different numbers.
Where it landed
A concept, self-initiated, with no client. It exists so a mobile handoff can be reviewed by using it rather than by imagining it.
The interface, running
This is the real thing, not a screenshot. Every control on it works.
Thursday
FitPulse
Tap an exercise to log a set
What you're looking at
A live mobile UI, not a screenshot. Log sets on the Today tab and the ring responds; switch tabs to see the weekly plan and volume history. Every control clears a 44px touch target and the whole thing runs on component state — the same patterns I hand off for React Native and Flutter builds.