Skip to content
Consumer app · Eleven build sessions, from first screen to TestFlight
1.0on TestFlight and ready for App Store review
Boltfri, a habit tracking app for iPhone logo

Boltfri, a habit tracking app for iPhone

The Boltfri home screen, with the current streak, longest streak and lifetime total, the support button and today's routines
Home. The streak, the record, and what is next today.
The Boltfri progress screen, a monthly calendar of tracked days with key stats beneath
Progress. Every day on the calendar, and the numbers that matter.
The Boltfri tools screen, with a personal plan, a daily lesson, phone controls and four focus games
Tools. A plan, a lesson a day, phone controls and four focus games.
The problem
An idea for a calm, grown-up habit tracker in a category full of gimmicks, and no app to show for it
What we built
A native iOS app, from onboarding to App Store build: streaks and milestones, daily check-ins, guided routines, a lesson a day, focus games, phone controls and cloud backup
What changed
A finished, testable app on TestFlight with real cloud backup, ready for App Store review
How long
Eleven build sessions, from first screen to TestFlight

What was capping them

Boltfri is a habit tracker for people who want to break a habit and keep it broken. The brief was clear about the feel. Calm and grown up in a category where most apps are either a streak counter with adverts or a gamified toy. The reference points were Calm, Headspace and Apple Health, not a game. What did not exist was the app.

What we built

A native iPhone app, built in eleven sessions and shipped to TestFlight.

Under it, a design system that keeps the whole thing consistent: one file of colour, spacing and type tokens, one icon set at one stroke weight, one haptics service so every tap feels the same, and spring animations with the bounce deliberately tuned out.

The last session was the one nobody sees. The app's backend had quietly been paused and its database turned out to have no tables, so we rebuilt the schema as versioned migrations with proper row level security, wrote a sync engine that backs up thirty kinds of local data with a three way merge so a phone and the cloud can never overwrite each other, and made sign up honest about whether it had actually finished. That went out as TestFlight build 14.

What changed

The idea is now an app that can be handed to a tester. It works fully offline, backs itself up when it can, and every screen holds to the same quiet standard. The remaining work is a device pass and the App Store listing, not the product.

Same problem, different business?

If you recognised yourself in this, the free audit is the fastest way to find out what a focused build would fix.

More work