Coach on the web
Next.js / Supabase
Planning, templates, calendars, progress review, trainer flows, and administration.
Independent product build
Coach: a cross-platform fitness product.
Coach is a personal fitness product I am building across web, iOS, and Android. It connects workout planning, active logging, progress, health data, and trainer workflows.
I built it solo, through an AI-native workflow, and it is live in invite-only beta with internal users. I define the product model, the interaction decisions, the platform approach, the data model, the implementation, and the criteria the personalized programs are evaluated against. The evidence here is the working build.
Open coachfitness.co.in
Coach for iOS
SwiftUI / HealthKit
Native workout logging, health insights, widgets, Live Activities, and personal training.
Coach for Android
Kotlin / Compose
Material 3 flows, local persistence, background work, secure storage, and Health Connect.
A working workout flow.
The walkthrough shows active set logging, rest, and progress. The adjacent screens show how health context and trainer workflows extend the same product.
What Coach currently covers.
Workout logging
Active sessions, set logging, RPE, rest timers, notes, resume states, and history.
Progress tracking
Volume, best lifts, recent exercise history, PR signals, and progression suggestions.
Health context
Apple Health, HealthKit, Health Connect, steps, workouts, energy, weight, sleep, HR, and HRV.
Trainer workflows
Trainer directory, packages, bookings, credits, chat, availability, and secure access control.
Product architecture
Supabase Auth, Postgres, RLS, invite-only flows, local demo mode, and platform configuration.
Payments and packages
Trainer packages, credits, checkout surfaces, and booking flow foundations.