PPL. Five hours to ship. Used six days a week.

The content was excellent. The experience was not.

I follow the Push Pull Legs program by Jeff Cavaliere (ATHLEAN-X), a structured six-day workout split. The program lives as long-form blog posts: exercise lists, sets and reps, variations, embedded form videos, and weekly structure. The content itself is great. Using it during a workout is friction.

Every gym session, on repeat

1. Open browser. Navigate to the blog page.
2. Scroll through a long article to find today's variant (Push 1, Push 2, Pull 1, etc).
3. Locate the specific exercise within that section.
4. Watch the form video.
5. Lock phone, do the set, unlock phone.
6. Scroll back to where you left off. Repeat. For every exercise. Every set.

There was also a persistent technical issue: after one embedded video, the next one wouldn't play without a full page refresh. That meant reloading mid-workout, losing scroll position, and starting the hunt over.

The whole cycle added 45 to 60 seconds of friction per exercise. Not catastrophic. Compounding. Over a seven-exercise session, five to seven minutes of fumbling instead of training.

Why existing apps didn't fit.

I'd used Strong, Hevy, JEFIT, and others over the years. Well-built products that solve general fitness tracking effectively. They didn't solve my specific problem.

• The exact ATHLEAN-X exercise variations often weren't available
• Exercise naming was inconsistent across platforms
• Custom superset flows and ramp-up structures couldn't be easily recreated
• Every app required me to adapt my program to its system, rather than supporting how I already train

I asked four friends following the same program how they dealt with it. Same frustrations. Scrolling, refreshing, lost position. One was manually writing sets and reps in his Notes app after every session. The pattern was clear. Same workflow. Same pain. Same unmet need.

A single, opinionated north star.

No setup. No scrolling. No searching. Open the app and today's exercises are right there with videos, logging, and nothing else. Friction reduction at every layer.

• Zero configuration during workouts. The app knows what day it is and what you should be doing
• One-tap access. No navigation required to start training
• No features that don't serve the workout. If it doesn't help you finish your session faster, it doesn't belong

Six features. Each one earns its slot.

What I cut, and why.

The discipline of staying focused on the primary use case mattered more than feature richness. Three things I deliberately did not build.

What surprised me

The rest timer was a feature I included almost as an afterthought. In practice, it transformed my workout flow. Before, inconsistent breaks: sometimes one minute, sometimes four, depending on how distracted I got. After, automatic, consistent recovery that kept sessions tight. I didn't anticipate it would become one of the highest-value features in the app.

Five users. The App Store was overkill.

Publishing to the App Store requires a $100/year developer account. Overkill for a five-person user base. Instead I installed it directly via Xcode: plug in their phone, hit Run, hand it back. The entire onboarding flow was under a minute. One friend uses Android. I converted the codebase and shared the APK in an afternoon. Same app, different platform.

No onboarding was required because the app does exactly one thing and does it obviously. There's nothing to figure out.

Both features shipped the same day they were requested.

That's the entire feedback loop. Ship. Observe. Listen. Ship again.

Launch to logged set, under ten seconds.

Drag your own screenshots or GIFs onto the slots below.

What this taught me about shipping.

Narrow scope is a feature, not a limitation

By building for one specific program and one specific group, I avoided the trap of building for hypothetical users. Every decision was grounded in real behavior I could observe directly.

Ship the smallest thing that solves the real problem

The app doesn't have AI, doesn't have social features, doesn't have detailed analytics. It has exercises, logging, and a timer. That's what was needed. That's what shipped.

Users reveal value you didn't design for

The rest timer, the import feature, the delete function. The most impactful additions either surprised me or came directly from users. Building something real and putting it in people's hands surfaces needs that brainstorming alone cannot.

Speed of delivery matters

A solution that exists today is more valuable than a perfect solution next month. The five-hour build time wasn't about cutting corners. It was about knowing exactly what to build, and not building anything else.

A small project. Transferable muscles.