Zzz
Docs

Best practices

The habits of people who ship: start small, test early, keep versions you can return to.

Start smaller than you think

The apps that reach the App Store all start the same way: one core action, done well. Build the version where a user can do the one thing your app promises, then grow it. "Log a workout and see my streak" ships; "a complete fitness platform" stalls.

Test on your iPhone early and often

Don’t wait until the end. Scan the QR code after every meaningful change and use the app like a stranger would (see how). Five minutes on a real phone catch more than an hour in the browser.

Lean on versions

Zzz keeps a version history of your project. Before a risky change ("redesign the whole home"), you can always come back to the previous state if you liked it better. That safety net should make you bolder, not careful.

Connect integrations at the right moment

  • Supabase early, as soon as your idea involves accounts or saved data.
  • RevenueCat once your core flow works and you know what’s worth paying for.
  • App Store Connect when you’re one week from wanting to ship.

Show it to someone before Apple sees it

Hand your phone to a friend, say nothing and watch. Where they hesitate is your next prompt. Three of these sessions beat any amount of self-testing.

Good to know

  • Keep a notes file of ideas as they come, and feed Zzz one at a time.
  • Ship, then iterate: an app in the store improving every week beats a perfect app that never launches.