Somebody opens your app for the first time. You have roughly a minute, probably less, before they decide whether this was worth it.
Most of the people who ever try your app will leave during that minute. Not because it's bad, but because they didn't get far enough to find out.
The moment it clicks
Every app has a point where someone goes "oh, I see." A note app, it's when they've written something and it saved without thinking about it. A photo tool, it's seeing their own photo look better. An invoice app, it's the first invoice going out.
Before that point the app is a promise. After it, it's useful.
The single most valuable thing you can do for a new user is get them there fast, and the second most valuable is remove everything standing in the way.
Worth naming yours explicitly, in one sentence, because everything about your first-run experience should be judged on whether it helps or delays that moment.
Every step loses people
Between opening the app and the moment it clicks, there's usually a sequence. Signup, email verification, a form, permissions, a tour, then finally the thing they came for.
Each of those loses a slice of people, and they multiply. Five steps at 80 percent each leaves you with a third of who you started with, and 80 percent is generous for a signup form.
So the question for every step is whether it earns its place, and the honest answer is usually no.
Do you need their name before they've seen anything? Do you need an account at all yet? Does the notification permission have to be asked for in the first ten seconds, before they know why they'd want it?
Most onboarding exists because the builder wanted the information, not because the user needed to give it. Anything you want but don't need yet can be asked for later, once they care.
Give before you ask
The pattern that works is letting people experience the value before requesting anything.
Let them use it. Let them create something. Then, when they've got something worth keeping, that's the natural moment to say "make an account so this doesn't disappear."
Now the account isn't a toll gate before an unknown experience, it's protecting something they already have. Same form, completely different willingness.
Empty screens are your best opportunity
A new user's first screen is empty by definition. No data, no history, nothing.
The lazy version says "No items yet." The useful version explains what this screen is for, shows what it looks like with something in it, and gives one obvious action.
This is prime real estate. It's the one moment you have their full attention and they're actively looking for what to do. A blank screen wastes it entirely.
Tours mostly don't work
The reflex when an app is confusing is to add a walkthrough. Five screens explaining the features before anyone's touched anything.
People skip them. And even when they don't, information given before it's needed doesn't stick, because there's nothing to attach it to.
If your app needs a five-screen tour to make sense, that's information about the app rather than a gap in the tour. Better to explain things at the moment they become relevant, one small hint at the point of use, and let the rest be discovered.
The number worth watching
Later, when you have users, the useful measure of all this is what fraction of new people reach that click moment.
Not signups. Not downloads. The percentage who actually got to the point where your app did something for them. That number tells you whether your first minute works, and it's usually much lower than people expect the first time they measure it.
A quick story. I rebuilt my app's onboarding to be less of a form and more of a conversation, asking a few questions that shaped what someone saw afterwards, so the first screen felt like it was already about them.
I still think that was the right instinct. But I want to be honest about the limit of it: I never watched a single stranger go through it. Every decision about which questions to keep, which to cut, where people would lose patience, was me guessing.
Onboarding is the part of an app most improved by watching someone use it for the first time. Ten minutes of watching a real person hesitate teaches you more than a week of your own reasoning.
If you want to design your first minute
Point two tends to be uncomfortable in a productive way. Most first-run flows have at least two steps that exist purely because the builder wanted them there.
Next: Free vs paid →
Go deeper: Chapter 10, Onboarding and Activation