PRODUCT DESIGN - iOS - BYLD MVP
Making workout tracking easier during real gym sessions.



Overview
BYLD is a mobile hypertrophy tracker designed to help users create routines, log workouts with minimal friction, and view their progress over time. The product structures the training experience to reduce decision fatigue, eliminate uncertainty during workouts, and build long-term consistency and confidence.
THE CHALLENGE
1. What is the core challenge behind workout tracking?
Intermediate gym-goers already understand the basics of training, but still struggle with structuring routines, maintaining consistency, and knowing if their effort leads to progress. The product challenge was not merely logging data, but helping users prepare for workouts, record sessions with minimal friction, and verify their performance gains over time.
Lack of Structure
Managing repeatable routines created unnecessary decisions before and during workouts.
Logging Friction
Recording sets, reps, weight, and exercises often interrupted the flow of active training.
Unclear Progress
Raw workout logs failed to communicate consistency or performance improvements over time.
TARGET USERS
2. Who are the target users and why prioritize them?
Based on secondary research, we segmented users by training experience to identify which group would benefit most from the first release.
| User Group | Likely Needs | MVP Priority |
|---|---|---|
| Beginners | Guidance, confidence, simple logging | Future iterationrequires heavy onboarding and education |
| Intermediate Users | Routine management, consistency, progress visibility | Primary Focus |
| Advanced Users | Deep customization, detailed analytics, flexible programming | Future iterationrequires complex customization tools |
PROBLEM DEFINITION
3. How was the core user problem defined?
We focused our problem statement on the specific friction experienced by intermediate gym-goers:
As an intermediate gym-goer, I struggle to train effectively because I lack the structure and feedback needed to understand what drives progress, resulting in inconsistent routines, wasted effort, and unclear results.
MVP SCOPE
4. How did we define the scope of the MVP?
The MVP was intentionally focused on the core workout loop: starting a session, following a routine, logging exercises, and reviewing progress. Any feature that did not directly support completing a workout, staying on track with a routine, or understanding progress was left out of the initial release.
Core Included Features
- Start Workout Flow
- Reduces setup friction so users can begin training immediately.
- Workout Logging
- Records exercises, sets, reps, weight, and duration.
- Routine Templates
- Helps users organize repeatable workout plans for consistent training.
- Workout History
- Enables users to review past sessions and maintain training continuity.
- Basic Progress Tracking
- Displays exercise stats, records, and performance changes over time.
COMPETITOR ANALYSIS
5. What did we learn from existing market competitors?
I evaluated three key competitors (Strong, Hevy, and Lyfta) across logging efficiency, routine creation, progress visibility, and ease of use:
| Competitor | What we learned | Opportunity |
|---|---|---|
| Strong | Offered fast set logging, but routine management and progress views felt dated. | Maintain fast logging speed while making routine and progress views easier to navigate. |
| Hevy | Strong social features and community sharing. | Keep the MVP strictly focused on individual training efficiency rather than social distractions. |
| Lyfta | Engaging visual muscle feedback. | Make progress visual and motivating, while keeping metrics clear and actionable. |
DESIGN DECISION
6. How did we balance familiarity with innovation?
The goal was to launch quickly, reduce unnecessary learning for users, and start validating the product through real usage. Instead of reinventing every interaction, I decided to use familiar patterns for established workout flows and focus innovation on areas where BYLD could create more meaningful value.
Direction 1 — Familiarity
Competitor research showed that many established fitness apps use similar patterns for high-frequency tasks such as starting a workout, logging sets, and reviewing previous performance.
For the MVP, I intentionally kept these interactions familiar so users could understand BYLD quickly without having to learn a new way of completing common tasks.
This also helped us reduce design and development time, launch sooner, and start learning from real usage.
Direction 2 — Innovation
I didn’t want to spend significant MVP time reinventing interactions that users already understood, especially before we had validated the core product.
Instead, I focused innovation on areas where BYLD could create more meaningful value and differentiation, such as helping users better understand their training through Premium insights.
CORE USER FLOWS
7. How do the core user flows guide the workout loop?
The interface supports three primary flows that mirror the natural training cycle:
Flow 1 — Start an Empty Workout
Supports flexible training by letting users add exercises and log sets with minimal friction as they go.
Flow 2 — Start from an Existing Routine
Reduces decision-making by giving users a structured, repeatable workout they can start and follow immediately.
Flow 3 — Review Progress
Turns workout history into clear performance insights, helping users see consistency, improvements, and personal records over time.
SUCCESS METRICS
8. How will we measure product success?
Success is evaluated across five key product behaviors:
| Product Goal | Metric to Track | Why It Matters |
|---|---|---|
| Help users start training | Start workout rate | Measures how easily users initiate a session. |
| Reduce logging friction | Workout completion rate | Measures whether users finish logging without abandoning mid-session. |
| Support consistency | Repeat workout rate | Evaluates long-term user retention and habit formation. |
| Support routine management | Routine creation / usage | Measures if users organize and reuse structured routines. |
| Improve progress visibility | Progress & history views | Measures how often users engage with their performance data. |
IN-GYM VALIDATION
9. How did we validate the experience in real workouts?
As both the designer and a regular gym-goer, I tested BYLD during my own workouts and gathered informal feedback from a small group of active gym users. The goal was to understand how the experience performed under real training conditions, where attention is limited and interactions happen quickly between sets.
Testing in context revealed friction that was difficult to identify from static screens alone. Users needed faster access to workout information, clearer visibility of their current state, and fewer steps to resume training after each rest period.
DESIGN DECISIONS
10. How did the gym context influence our design decisions?
One repeated friction point during in-gym testing was the need to reopen the app between sets just to check basic workout information, such as the current exercise, set progress, or remaining rest time.
This insight led us to introduce Live Activities, bringing key workout information directly to the Lock Screen and Dynamic Island. Users could check their current exercise, active set, and rest timer at a glance without navigating back into the app.
By reducing unnecessary phone interactions, Live Activities helped users stay focused, maintain workout flow, and return to the next set more quickly.
LEARNINGS & NEXT STEPS
11. What are the next steps after validating the core experience?
Once live usage validates the core logging and routine management loop, future product releases will focus on:
Deeper Progress Insights: Providing richer context on performance trends over time.
Advanced User Support: Expanding customization tools and detailed analytics once the foundational experience is established.
