LunaFit App Case Study
LunaFit taught me how to close the design–dev gap, ship faster with a design system, and let research drive the product.
- 01Experience redesigned to drive behavior
- 02Seven chapters of building the system
- 03Research & data that shaped the product
LunaFit Experience
Experience redesigned to drive behavior.
Beat 01
LunaFit
An AI-powered fitness platform built around a coach-first experience that replaces traditional menus with guided interaction. Every UX decision was focused on increasing engagement, clarity, and long-term habit formation.
Beat 02
From form fatigue to guided momentum
Replaced a long, static onboarding flow with a conversational, coach-led experience that adapts in real time.
- Reduced 17-step form into dynamic, step-by-step guidance
- Asked only what’s needed, when it’s needed
- Shifted onboarding from setup to first moment of value
- Users begin interacting immediately instead of filling forms
Beat 03
Designed for in-the-moment use
Optimized core workout flows to support real usage during workouts, not just static UI clarity.
- Prioritized current lift over history in weight logging
- Reduced taps and cognitive load during sets
- Surfaced progress in real time
- Validated through usability testing with strong user preference
Beat 04
From feature to constant presence
Transformed the coach into a persistent, state-driven system rather than a secondary feature.
- Always-visible coach replaces deep navigation
- Voice and text inputs unified into one interaction model
- State-driven responses (idle, talking, listening)
- System feels responsive and alive instead of scripted
Beat 05
Making progress feel visible
Addressed early drop-off by designing for motivation and progression.
- Introduced streaks, levels, and phases
- Reframed workouts from repetition to progression
- Reinforced consistency through small wins
- Designed specifically to improve early retention
Beat 06
Experience to behavior change
These improvements shifted the product from a tool into a system users consistently return to.
- Increased onboarding clarity and completion
- Reduced friction during workouts
- Stronger feedback loops for motivation
- Improved retention signals and engagement
Journey & Vision
One designer. Seven chapters of building the system.
Beat 01
Day 1, Week 1.
I joined; the previous designer trained me for a week, then left. I inherited 300+ unlabeled frames and a live product.
Beat 02
Execute fast, no system.
No components, no time to organize. I redesigned screens under visual restrictions, while shipping weekly.
Beat 03
Organize by feature.
First pass of structure: screens grouped by feature, labeled, searchable. Not a system yet, but navigable.
Beat 04
Many hands, many branches.
Marketing asks. Investor asks. Dev asks. Stakeholder asks. All landing on one designer at once.
Beat 05
The drift.
Over time, what's in Figma ≠ what's in the app. The drift is what forced the next phase.
Beat 06
Building a refined component system.
Little by little. From screens to components. Shared patterns began replacing one-off decisions.
Beat 07
The vision.
A token change in Figma propagates through Code Connect, auto-generates a PR, and devs merge. Zero manual handoff.
LunaFit Research