Personal product build
Built Coach from scratch: a cross-platform fitness product for planning workouts, logging sessions, tracking progress, connecting health data, and supporting personal training workflows.
Open coachfitness.co.inCreate a real workout product that can plan routines, guide active sessions, track progress, connect health data, and support trainer workflows across web, iOS, and Android.
3
Web, iOS, and Android, each with platform-native surfaces
2
Apple HealthKit and Android Health Connect, feeding one data model
Invite-only beta
Live at coachfitness.co.in with internal users
Coach is live at coachfitness.co.in in invite-only beta with internal users. Built solo through an AI-native workflow. The screenshots on this page are real captures from the current build; there is no market traction to claim yet.
Start with the active workout, log the set in the moment, then move into health context, progress, and coaching. This walkthrough puts the interaction model ahead of static concept screens.
Bring today's workout and the next meaningful action into a single starting point.
Log weight, reps, effort, and sets without losing focus on the exercise in front of you.
Connect workout history with health, progress, and trainer context once the session is complete.
Workout products often split planning, active logging, progress review, trainer support, and health context across separate tools. Coach explores what a single cross-platform product system can look like when those jobs are connected.
The web app handles hosted workflows such as onboarding, templates, workout sessions, calendar, progress, friends, profile, admin, and trainer flows. Native apps bring the experience closer to the workout with Apple Health, Health Connect, widgets, Live Activities, and device-specific interaction patterns.
The part I would put in front of a hiring team is not the app, it is the criteria: I defined how program-allocation accuracy is evaluated for personalized plans, the same way I define acceptance criteria for the AI systems I ship at work.
The Next.js app uses App Router, Vercel, Supabase Auth, Supabase Postgres with Row Level Security, mobile web/PWA behavior, demo mode, trainer directory, bookings, chat, packages, and owner/admin workflows.
The SwiftUI app includes auth/session restore, onboarding, tabbed navigation, workout start/resume, set logging, progress dashboard, Apple Health steps and insights, Live Activities, Dynamic Island surfaces, widgets, and personal training discovery.
The Android surface uses Kotlin, Jetpack Compose, Material 3, Room, WorkManager, secure crypto storage, Health Connect/Fitness libraries, Supabase auth/postgrest, and a configurable Coach web URL.
Coach is where I test product decisions end to end: from the user workflow and platform choice to implementation details and the experience in someone's hand. It is also why I can hold a technical conversation about the systems I spec at work.
Coach is one product with platform-specific experiences across web, iOS, and Android.
Web
Mobile-first web/PWA with invite auth, onboarding, workout logging, templates, library, calendar, progress, friends, profile, admin, and trainer workflows.
iOS
Native iOS surface with onboarding, workout logging, HealthKit steps and insights, progress dashboard, widgets, Live Activities, Dynamic Island, and personal training entry points.
Android
Android app configured with Material 3, Room, WorkManager, secure storage, Health Connect/Fitness, Supabase auth/postgrest, and web bridge URL.