Ideas in.
Products out.

Strength logging is a crowded shelf, and almost every app on it runs on the same engine: streaks, badges, a feed. So before designing anything, I sat down with four serious lifters. The same answers kept coming back. They already track their training. They judge a set by the reps they had left in the tank, not just the weight on the bar. And every app they'd tried buried that signal.

I'm one of them, which helped me hear the thing nobody said out loud: a serious lifter already knows whether they showed up. That set the bet early. Build for the lifter who already trains, and let the casual market keep its streaks.

The problem wasn't motivation, and it wasn't more data. It was proof: a lifter can't easily see whether the work is working. Two decisions locked here and never moved. Reps-in-reserve sits at the centre of every logged set. And strength over time is shown honestly, so an easy day is never dressed up as progress.

With the problem fixed, the open question was how to show progress without lying about it: an honest max estimate adjusted for effort, stall detection that watches the trend, muscle balance and personal records by rep range. I didn't decide alone — once early users were in the private beta, a feature survey ranked what got built. I also built a streak counter, liked it, and killed it: a streak is the exact game Notch exists to end.

Converging was mostly subtraction. The exercise library was cut to the lifts a serious program actually uses, and features I was excited about moved to after launch. I designed every screen and directed AI dev tools through the build, so the design lives in the code and nothing dies in a hand-off. The launch metric is retention, not installs.

• doneOBSIDIAN system and every screen — built and working.
• doneBrand and waitlist live at notchlift.app.
• doneFull QA pass — green test suite, a security review, a class of crashes designed out.
• nowPrivate beta with real lifters, last pre-launch fixes.
• nextApp Store submission and the 2026 launch.

The homepage was built for people who already knew the brand, not the cold traffic actually landing on it from search and ads. It opened with sixty-plus challenge cards in one dense grid. No pitch, no explanation, nothing telling you where to look first. The analytics said it plainly: first-timers arrived cold, met the wall of choices, and left without picking one.

scroll ↕

They weren't short on challenges. They were short on a path. That reframed the whole brief: stop treating the site like a catalogue and start treating it like a sequence. Lead with the pitch, feature a handful of challenges instead of all of them, put the proof near the top, and give each section room to be read at a glance.

Working with a developer and a CRO, I designed against that sequence: a homepage that opens with the pitch, a five-step how-it-works, and proof — 450k members, an 87.93% completion rate, press logos — before a short list of popular and licensed challenges. We kept the full catalogue, one click away, so nothing was lost, only reordered. Underneath it, a shadcn design system so design, dev, campaign and creative teams work from one source.

scroll ↕

The A/B test settled the argument: organic click-through rose 68% against the old homepage. The full catalogue never left, it just stopped being the first thing anyone saw. Moving it one click away, and giving the top of the page a pitch and proof instead, was most of where the 68% came from.

Three plans sat in three separate tables, each with its own call to action. The page competed with itself, asking people to solve a comparison puzzle at exactly the point where hesitation costs the most: the step where money changes hands.

Three tables side by side turns picking a plan into comparing three plans first. So the brief narrowed to one sentence: make the page ask one decision at a time — which plan, then one button.

Compress three tables into one plan selector with a single button underneath. Same comparison, one control instead of three. The narrowing happened live: four to five A/B rounds with a developer and a CRO, each version tested against the last.

One selector, one button, +11% conversion — settled by the A/B test. Pages stop competing with themselves when they ask one decision at a time. Same fix as the homepage, a different page.