Onboarding That Actually Converts: The 60-Second Rule

You spent three months building the app. Someone installs it. They have your icon on their home screen. Sixty seconds later, they're gone — and they never come back.

This is the reality for ~80% of new app installs across every category. The first session decides whether you ever see that user again. Get the first sixty seconds right and your D1 retention triples. Get it wrong and no marketing budget on earth saves you.

The good news: most indie onboarding flows fail in the same three ways, and the fix is mechanical.

---

The 60-second rule

A user gives you 60 seconds to deliver one specific thing: a moment where they understand, viscerally, that your app does something useful for them. Not a tour. Not a feature list. The actual moment.

For Slothy (todo + planner): tap one button → first todo created → see it on tomorrow's screen. That's the moment.

For Excuse Caddie (golf excuse generator): tap → excuse appears → laugh or share. That's the moment.

For a B2B SaaS: paste one URL → see the audit result → that's the moment.

If your onboarding takes longer than 60 seconds to reach the moment, every extra second is a cliff. Real measurement: 7-second drop-offs at every screen until they hit value.

---

The three failure modes

Almost every onboarding flow fails one of these:

1. Asking for permissions before value

Login, email signup, push notification permission, location access, paywall — anything that interrupts the path to value before the user has seen value.

The fix: defer everything. Show the value first. Ask for permissions when the user does the action that needs them, not as the opening move.

Example: a meditation app that asks for push permission on screen 2 ("so we can remind you") will get ~20% accept rate. Same app asking for push permission AFTER the user completes their first session ("want a reminder for tomorrow?") will get 60%+.

2. Tour-style walkthroughs

Five-screen tutorials with "Tap here, then tap here, then tap here." Users skip them, dismiss them, or worse — sit through them and forget everything by screen 3.

The fix: no tour. The app teaches itself through use. If your UI needs explanation, the UI is the problem, not the user.

The only exception: a single contextual tooltip when a user reaches a screen for the first time and the most-important action isn't obvious. One tooltip. Not five.

3. Empty states that say "nothing yet, get started by..."

This is a tax. Every empty state asks the user to do work before they get anything back. The user has zero context for what "good" looks like.

The fix: pre-fill the first thing. Show a sample todo. Generate a sample excuse. Auto-populate the first chart with demo data they can delete. The user's first session has content from second one.

---

The structure that works

A working indie onboarding has at most three things:

1. Hook screen (5 sec)
   - 1 sentence on what the app does
   - 1 primary button to start

2. Value moment (15-30 sec)
   - User does the action
   - Sees the result
   - Aha

3. Permission ask (5-10 sec, optional)
   - Only if needed for the next action
   - Framed as "want X? we need Y"

That's it. No accounts. No email capture. No tour. Account creation can come later (after session 2, after the third action, after they've explicitly invested something).

Three screens, sixty seconds, one moment.

---

How to find your moment

If you don't know what your value moment is, here's the test:

If a user does exactly ONE thing in your app and you had to pick what it would be, what is it?

That action is your moment. Everything in onboarding should drive toward it.

For most indie apps the answer is obvious within 5 minutes of thinking. If you can't answer it, your app might not have a value moment yet — which is a deeper product problem, not an onboarding problem.

---

Metrics that matter

Track these from day one (PostHog free tier handles all of it):

• Time to first action. From app open to first meaningful tap. Goal: under 30 seconds. If it's over 60, your onboarding has friction.
• D1 retention. Percentage of new installs who come back the next day. Indie baseline: 20–30%. Above 40% means onboarding is working.
• Onboarding completion rate. Percentage of new installs who reach the value moment in the first session. Goal: 70%+.
• Permission accept rate. Percentage who allow push/location/etc. when asked. Goal: 40%+ for push. If yours is below 20% you're asking too early.

If you only track one: D1 retention. Everything else is upstream of it.

---

The receipts: what we did

Both fixes were under 2 hours of work. Both moved D1 retention more than any feature we added in the following month.

---

When to add the gates back

Eventually you need accounts, email capture, paywalls. The point isn't to never ask — it's to ask AFTER value has been delivered, not before.

A reasonable progression:

• Session 1: value moment only, zero asks
• Session 2: optional account creation, framed as "save your progress"
• Session 3: push permission ask in context
• Day 7+: paywall for advanced features (if applicable)

This sequence assumes the value moment landed. If your D1 retention is below 20%, no progression in the world will save you — fix the moment first.

---

The one thing to test this week

Reset your app on a fresh device. Time yourself from icon tap to value moment. Anything over 60 seconds: cut.

Most indie devs find this exercise reveals one specific screen that's eating 20-40 seconds for no reason. Removing that one screen often beats months of feature work for retention.

The product is good. The marketing brought them in. Don't lose them in the first 60 seconds because of an onboarding flow you wrote at 2 AM the week before launch.