
iOS Mobile App · Fitness + Gamification · 2023 · Sunset
BurnFriends
iOS fitness app: friends compete on a leaderboard, a tamagotchi-style phoenix thrives when you walk and wilts when you don't. Six weeks from idea to App Store. 200 concurrent users.
Visit the live productAn idea is hatched (on a phone call with my best friend)
One day, during my usual daily call with my best friend David, I found myself reminiscing about the workout routine my dad and I had during the four months I spent back home due to the pandemic. It started with daily walks. Soon enough we added spin bikes. Before we knew it we had a full-fledged routine — every morning, a spirited spin class followed by a brisk 6-mile walk, evenings dedicated to riding while binge-watching the entire Marvel series in chronological order. Our motivation was unwavering.
But as the world returned to normal, I moved back to San Francisco. Keeping up that momentum became a challenge. We tried Apple Watches, ring-sharing, auto-generated motivational messages — everything to keep the energy alive. Nothing stuck.
That's when David mentioned wanting an easy way to get his friends to walk more together. They'd tried sharing Apple Watch rings, using various fitness apps. The problem wasn't tracking. It was motivation. Nothing made walking *fun*.

The name? Straightforward. Burn calories, with friends. Wordplay aside, there's depth to it — after a setback, we rebound, much like a phoenix.
Three north stars (and the part where we got stuck)
Before any code, we locked three rules. Anything proposed in week 2 onward got measured against them. If a feature didn't serve all three, it was cut.
Prototyping? First go was all Google Sheets. Quick and familiar. Second round we stepped it up — merged a basic step-tracking iOS scaffold we found with no-code magic from Make.com, linking Google Sheet and Firebase. We were on the move.
Everything is all fine and dandy until you actually get started. Then it's just one obstacle after the next. If it wasn't obstacles, it was us buried deep in endless tinkering, forever refining, waiting for that perfect plan to emerge.

The reframe (a ceramics teacher saves the project)
Have you ever heard that ceramics teacher story? The one where half the class is graded on the quantity of their pots and the other half on quality? Spoiler: the students focused on quantity ended up making the best pots. Their learning curve skyrocketed with each pot.
This is essentially the 'just ship it' mindset. The more you iterate and share your work, the more feedback you receive, and the faster you improve.
This shift was crucial. Instead of waiting for perfection, we embraced progress. Every version we released, every piece of feedback, brought us closer to what BurnFriends was meant to be.
The structure (6 weeks of forced ship checkpoints)
We joined Buildspace's Nights and Weekends program — a structured sprint designed to take an idea from zero to shipped in 6 weeks. Friday demos. No exceptions.

By the end of Week 6: 200 concurrent users actively running fitness challenges with their friends. Live on the App Store. Six weeks from a call with David to a real product in real people's hands.
What we'd do differently (the honest part)
BurnFriends is sunset now. The cohort ended, life happened, the app didn't have a path to a real business model and we didn't force one. That's fine — we built it to prove we could ship together, not to run it forever. The 200-user spike was the win. The lesson: shipping the thing and finishing the thing are different jobs, and BurnFriends only got the first one.
Perfect is the enemy of done.
The build pattern — three north stars, weekly ship checkpoints, AI/no-code to ship something embarrassing fast, then iterate — is the pattern The Ship It System codifies today. BurnFriends was built before the templates were named. The methodology was the same.
Shipped
Dated artifacts, in order.
- 2023-08 · Week 1Idea locked. Three north stars (Fun, Easy, Social) committed.
- 2023-08 · Week 2Google Sheets prototype + Make.com no-code automation linking Sheets ↔ Firebase. First version friends could actually use.
- 2023-09 · Week 3Public pitch + early user outreach. Started the feedback loop.
- 2023-09 · Week 4Native iOS rebuild — Swift/Xcode + Firebase. Tamagotchi phoenix mechanic added.
- 2023-09 · Week 5Push for users — word of mouth, leaderboard challenges with real friend groups.
- 2023-09-28 · Week 6Shipped to App Store. 200 concurrent users actively running fitness challenges with friends. ↗
Reference — templates fired
What the system actually did, step by step.Expand →
T04 Validation Scorecard
Validated 'motivation > tracking' against real lived experience — Apple Watch ring-sharing, MyFitnessPal, ad-hoc text accountability had all failed. The tamagotchi-phoenix visual feedback scored highest on emotional pull.
T05 One-Page Scope
Fun, Easy, Social — three north stars. Anything proposed in week 2+ got measured against all three. If it didn't serve all three, it was cut.
T07 Scope Guillotine
The killable thing: waiting for the perfect plan. Forced Round-1 prototype to be a Google Sheet. Round-2 a Make.com / Firebase hack. Both shipped before anyone wanted them to.
T08 10-Day Sprint Plan
Mapped onto the Buildspace 6-week structure: Ideas → Prototype → Audience → Iterate → Growth → Demo. Forced Friday ship-or-don't-ship checkpoint every week.
T10 Stuck Toolkit
Diagnosed the 'endless tinkering, waiting for the perfect plan' loop. The ceramics-teacher reframe (quantity beats quality on the learning curve) was the unstick.
T15 Weekly Ship Check
Friday demo every week. 'What did we ship this week?' Six demos in six weeks. The forcing function that produced 200 real users at the end.
Honest note
What this case study isn't.
BurnFriends shipped in 2023, before The Ship It System's templates were formalized — the original Medium writeup (published Sep 28, 2023) doesn't reference T01–T25 because they didn't exist yet. The mapping above is retroactive: the methodology was the same, the names came later. The app itself is sunset (no business model, no fundraising, no path to scale — and we didn't force one). The 6-weeks-to-200-users outcome is documented and verifiable. Read the unfiltered version in Molly's voice at the link above.
Last updated 2026-05-17.