Designing app onboarding that people do not skip
How to design app onboarding that gets people to something useful quickly, asks for permissions at the right moment and avoids long tutorials.
The best onboarding is the app itself, working, with as little as possible standing in front of it. Someone has just downloaded your app because they want to do a thing. Every screen between the icon and that thing is a toll booth.
Most onboarding fails because it is designed around what the business wants to say. Good onboarding is designed around what the person came to do.
What is the first useful moment?
Before designing any welcome screen, name the first moment your app is useful to a new person. For a cafe ordering app, it is seeing the menu and tapping "add" on a coffee. For a physio exercise app, it is watching today's first exercise. For a tradie's quoting tool, it is a finished quote ready to send.
Then count how many screens sit between opening the app and that moment. Write the list out. It often looks like this:
- Splash screen
- Three slides explaining features
- Create account
- Verify email
- Allow notifications
- Allow location
- Choose preferences
- Finally, the menu
Seven steps before a flat white. Your job is to cut that list as hard as you can, and to move what remains to the point where it makes sense.
Why do people skip the tutorial slides?
Because they have learned that tutorials are rarely necessary and never brief. Swipe, swipe, swipe, "Get started". Nobody reads them, and the few who do forget the contents by the time they reach the screen being described.
We usually suggest dropping the slideshow entirely. If the app needs explaining, try these instead:
- Teach in place. Show a short hint next to a feature the first time someone meets it. "Swipe left to mark a job done" is useful on the job list. It is noise on a welcome slide.
- Use sensible defaults. Pick the nearest store, the most popular option, the standard settings. Let people change them later.
- Make the first screen self explanatory. A clear heading, an obvious main button and a little sample content do more than any tour.
- Offer help, do not force it. A "show me around" link for those who want it.
When should you ask people to sign up?
As late as you can get away with. An account wall on the first screen asks for trust before you have earned any.
Let people browse first. Say you run a florist with an ordering app. Someone should be able to look through arrangements, choose one, pick a delivery date and write a card message before being asked for a name and email. By then they have invested a few minutes and the request has an obvious purpose: we need to know where to send the receipt.
Some apps do need an account from the start, such as a patient portal holding private records. Even then, keep the form short, explain in one line why it is needed, and hold everything optional until later.
How should you ask for permissions?
Badly timed permission requests are the fastest way to lose a new user. A system pop up asking for location, camera, contacts and notifications in the first ten seconds feels like a stranger asking for your house keys.
A few rules we stick to:
- Ask at the moment of need. Request the camera when someone taps "scan receipt". Request location when they tap "find my nearest clinic".
- Explain before the system prompt appears. Show your own short screen first: "We use your location to show the closest store. We do not track you in the background." Then trigger the official prompt.
- Ask for one thing at a time. Never stack requests.
- Keep working if they say no. Offer a manual option, such as typing a postcode. Do not punish the refusal.
- Leave notifications until there is something worth notifying. After a first order is a natural moment: "Want a message when it is ready?"
What should stay in onboarding?
Not everything can be cut. Keep a step if skipping it would leave the app broken or empty.
A personal trainer's app might need to know a goal and a fitness level, because without them it has nothing sensible to show. That is fine. Ask two or three quick questions, make each one a single tap where possible, show progress, and let the person skip anything that is merely nice to have.
The test for each step is simple. Does the person get something better immediately because they answered? If yes, keep it. If the answer mostly benefits your marketing list, move it or lose it.
A pre launch checklist
Run through this before you ship.
- Can a new person reach the first useful moment in under a minute?
- Can they look around before creating an account?
- Is every permission requested at the point it is needed, with a plain reason?
- Does the app still work if every permission is refused?
- Is there anything on screen that a returning user would have to tap past again?
- Have you watched three people who have never seen the app go through it, without helping them?
That last one is the real test. Hand someone your phone, say "have a go", and stay quiet. Where they hesitate is where your onboarding needs work.