Your AI Fitness Companion
AI Gym Bro
AI Gym Bro represents the kind of work I love: blending AI, UX, personality, and mobile development to create experiences that feel human and useful. It's not just a fitness tracker. it's a coach who knows your abilities, a cheerleader who has your back, a personal trainer who reminds you that it's leg day, no matter how much you want to skip. And it's an example of how AI can make everyday tasks more fun and individualized.
What it does
A conversational AI fitness tracker where users log workouts by chatting with an enthusiastic "gym bro" personality. It uses GPT-4o-mini to parse natural language into structured workout data, track personal records, and provide motivational feedback.
Why I built this
Every fitness app I tried felt like a spreadsheet. I wanted something that felt like texting a friend who happens to be really into lifting. Something that would remember my PRs, call me out when I skip legs, and actually make logging a workout feel fun instead of like homework.
Creative process
I started by thinking about the voice. Before writing any code, I wrote sample conversations. what would this AI say when you hit a new PR? What about when you log a half-hearted workout? The personality came first, and the architecture followed. I wanted every interaction to feel like it came from someone who genuinely cares about your progress.
Technical decisions
Flutter for cross-platform mobile, Python Flask for the backend API, PostgreSQL for structured workout data, and OpenAI's API for the conversational layer. I chose Flask for its simplicity. this app needed to be fast to iterate on, not over-engineered.
AI integration
The AI layer does more than chat. It parses messy natural language ("did 3 sets of bench, 185 for 8 reps, then dropped to 135") into structured data, detects personal records automatically, and adapts its motivational tone based on workout patterns.
How it works
Users type their workouts in natural language. The AI parses the input, extracts exercises/sets/reps/weight, stores it in PostgreSQL, checks for PRs, and responds with personality. The backend handles all the data logic while the AI handles the conversation.
What I learned
Personality is a feature, not a gimmick. Users kept coming back not because the tracking was better than competitors, but because the experience was more enjoyable. I also learned a lot about prompt engineering. getting an AI to be consistently encouraging without being annoying is harder than it sounds.

