Fitness Pace brings the parts of a training week into one place: decide what to do, record what happened, and use the result to plan the next session. Workouts, food, progress, and conversations share the same context. The product grew from PeerFit into a fitness companion with a clearer identity and an optional coach called PACE.
I built the Expo and React Native application alongside its TypeScript API. A person can choose a starter workout, adjust the session, log sets, and return to unfinished work. Food logging and meal planning sit beside weight trends and private progress photos. Community spaces and gym-buddy connections add a social layer without making every part of training public.
A coach with permission
PACE can help explain a plan, discuss a meal, or work through a training question. The server assembles the relevant account facts and controls access, usage, and actions. Coaching consent and action approval stay explicit. A conversation should help someone make a decision; it should never quietly make an account change on their behalf.
The app has Full, Reduced, and Off motion preferences. Workout artwork, transitions, and feedback follow that choice. Labels and touch areas remain stable while the surrounding artwork moves, and saved sessions remain understandable when motion is disabled.
The product around the app
The Fitness Pace website introduces the app through a short goal-and-routine quiz, real product screens, and an illustrated guide. The quiz produces a planning estimate from explicit answers. Visitors can revisit their choices or go straight to the guide.
The website is public. Android tester builds and a signed release candidate exist; public store availability is a separate step. The current work continues to refine the experience across training, coaching, and everyday return visits.