Onboarding Screen Design: The 2026 Mobile App Playbook

This playbook is for founders, PMs and designers who want new users to reach the moment where your app clicks, and come back the next day. You'll get the six onboarding patterns that work, when to use each, how to ask for permissions without getting denied, exact specs and copy templates, the metrics to measure, and a checklist to review your own flow.

TL;DR: Onboarding isn't a tour, it's the shortest path to a user's first success. Show value before asking for anything, collect only what personalises the experience, request permissions in context with a short primer, and measure activation, not just how many people tap "Next".

What onboarding is for

Onboarding covers everything between install and the moment a user gets real value for the first time, often called the "aha moment" or activation. For Duolingo, that's finishing a first lesson. For Spotify, it's hearing music you like. For a budgeting app, it's seeing your real spending in one place.

Good onboarding does three jobs:

1. •Orient: what is this app and why should I care?
2. •Set up: gather the minimum information needed to make the app useful.
3. •Activate: get the user to their first success as quickly as possible.

Everything else, such as feature tours, account creation, notification permissions or paywalls, should be judged by whether it helps or delays those three jobs.

The six onboarding patterns

Most strong apps combine two or three. Duolingo pairs a personalization quiz with try-before-sign-up. Notion uses templates and contextual tips. Banking apps combine account setup with a reassuring benefit screen.

1. Benefit carousels

The classic three swipeable screens with an illustration, a headline and a line of copy. They work when the app's value needs explaining before setup makes sense, and they fail when they describe features instead of outcomes.

Rules for carousels:

• •Three screens or fewer. If you need more, the product message isn't clear yet.
• •One idea per screen, written as an outcome: "See where every dollar goes", not "Transaction categorisation".
• •Always show "Skip" and page dots.
• •Put the main button at the bottom in thumb reach.
• •Let the last screen lead directly into the first real action.

Honestly, many apps can drop the carousel entirely. If your App Store screenshots already sell the value, a carousel repeats them.

2. Personalization quizzes

A short set of questions that changes what the user sees next: goals, level, interests, schedule. Duolingo asks what language you want to learn, why, and how much time you have per day. Pinterest and Spotify ask you to pick topics or artists so the first feed isn't empty.

Rules for quizzes:

• •Every question must visibly change the experience. If an answer isn't used, cut the question.
• •Use large tappable cards or chips, not dropdowns.
• •Show progress (a thin bar at the top) and let people go back.
• •Reflect answers back: "Great, we've built a 10-minute daily plan for Spanish travel phrases."
• •Keep it short for most apps. Some health and fitness apps run long quizzes successfully because the answers feel like a personal assessment, but they invest heavily in making each step feel worth it.

3. Try before sign-up

Let people use the core feature before asking them to create an account. The account then protects progress they already care about, which makes sign-up feel like a benefit instead of a toll.

This is the single most effective change for many apps. Apple's App Store Review Guidelines also say that apps shouldn't require registration for features that don't need an account. When you do ask, make it fast; our login screen design guide covers passkeys, social sign-in and email-first patterns.

4. Account and data setup

Some apps can't deliver value without setup: a banking app needs identity verification, a budgeting app needs a bank connection, a team tool needs a workspace. Make it feel like progress:

• •Explain why each step is needed in one line.
• •Show a step count ("Step 2 of 4") and estimated time ("Takes about 3 minutes").
• •Save progress so people can leave and resume.
• •Let people explore with sample data while verification completes.

Revolut and Monzo turned identity verification, traditionally a painful branch visit, into a guided in-app flow with document and selfie capture. The pattern to borrow is clear framing at each step, live camera guidance and immediate feedback when a photo is unusable.

5. Interactive walkthroughs

Instead of telling people how the app works, have them do a real task with light guidance: "Tap here to add your first habit." Done well, the user finishes onboarding with real data in the app. Done badly, it's a forced tutorial that people tap through. Keep each step to one action, let users exit any time, and never block the interface with a full-screen overlay for more than a moment.

6. Contextual onboarding

Teach features when they become relevant instead of front-loading them. A tooltip appears the first time someone opens the editor; an empty state explains what a screen is for and offers the first action. Empty states are the most underrated onboarding surface, because every new user sees them. Each one should have a short explanation, a simple illustration or icon, and one primary button.

Asking for permissions without getting denied

Permissions are where many onboarding flows quietly fail. On iOS, the system prompt for notifications, location, camera, contacts or tracking appears only once; if the user denies it, they have to find your app in Settings to change their mind. Android 13 and later also require a runtime permission prompt for notifications.

The permission priming pattern

1. •Wait for context. Ask for camera access when the user taps "Scan receipt", not on launch.
2. •Show a primer screen first. Your own screen explains the benefit in one sentence with a clear illustration: "Get a reminder at 8pm so you don't break your streak."
3. •Offer two buttons: "Turn on reminders" (which triggers the system prompt) and "Not now" (which doesn't).
4. •If they say not now, ask again later at a natural moment, such as after their third completed session.
5. •If they denied the system prompt, show a gentle in-app banner with a button that opens your app's Settings page.

App Tracking Transparency

If your app tracks users across other companies' apps or websites, iOS requires the App Tracking Transparency prompt. You can show a primer before it, but Apple's guidelines don't allow incentives for allowing tracking or designs that mimic the system prompt. Keep the primer honest and plain.

Permission timing cheat sheet

Where the paywall goes

Subscription apps face a real choice: show the paywall at the end of onboarding, or after users have experienced the product. Many subscription apps show a paywall straight after the personalization quiz, while the user is most motivated, and always with a clear way to continue or close. Others wait until a user hits a premium feature. Neither is universally right; test both. Whatever you choose, state the price, trial length and billing terms plainly. Meditation apps are a good study here; our guide on meditation app design covers trial paywalls in a wellness context.

Specs for onboarding screens

Keep headlines and buttons clear of the Dynamic Island, notch and home indicator; you can check placements with the notch and safe area simulator. Large, short headlines read best; our mobile app typography guide covers sizes and line heights in detail. If your app has a launch screen before onboarding, keep it simple and fast; the splash screen generator creates the required assets.

Copy templates

Copy does more work in onboarding than illustration. Use these starting points:

Welcome headline: "[Outcome] in [timeframe]" → "Speak basic Spanish in 3 months"

Benefit screen: "[Verb] your [thing] [benefit]" → "Track your spending without spreadsheets"

Quiz question: "What brings you here?" / "How much time do you have each day?" / "What's your level?"

Reflection after quiz: "Got it. We've set up a [plan] for [goal]."

Account prompt after value: "Save your progress. Create a free account so your streak is safe on any device."

Notification primer: "Want a nudge at [time] tomorrow? You can change this any time."

Empty state: "No [items] yet. [One line on why they're useful.] [Create your first item]"

A worked example: a habit tracker onboarding

Here's a complete flow that applies the patterns above. It has seven screens, and the user creates a real habit before signing up.

1. •Welcome: "Build habits that stick" with one illustration and a "Get started" button. No carousel.
2. •Goal picker: "What do you want to improve?" Chips: Health, Focus, Sleep, Fitness, Learning, Mindfulness. Multi-select.
3. •Suggested habits: Based on the goal, three suggested habits with a toggle each, plus "Add your own".
4. •Schedule: "When will you do it?" Morning, Afternoon, Evening, plus a time picker.
5. •First check-in: The home screen with the new habits, and a tooltip: "Done one today? Tap to check it off." This is the aha moment.
6. •Notification primer: "Want a reminder at 7:30am tomorrow?" with "Turn on reminders" and "Not now".
7. •Save progress: "Keep your streak safe" with Sign in with Apple, Google and email.

You can generate a first draft of a flow like this in floow from the screen list above, then adjust copy and order as you test. Screens 1–5 deliver value before anything is asked; screens 6 and 7 ask only once there's something worth protecting.

How to measure onboarding

Measure each step, not just the start and end.

Define your activation event precisely, such as "completed first lesson" or "checked off a habit on day one". A flow with a high completion rate but low activation is a flow people are tapping through without understanding.

Experiments worth running

• •Remove the carousel entirely.
• •Move account creation after the first success.
• •Cut the quiz to its three most impactful questions.
• •Move the notification primer from onboarding to after the first success.
• •Show a paywall after onboarding vs. on first premium feature.
• •Replace a feature tour with one interactive first task.

Common onboarding mistakes

1. •Asking for an account on screen one. The most common and most costly mistake.
2. •Requesting every permission at launch. Users deny what they don't understand.
3. •Feature tours instead of outcomes. Nobody installs an app to learn its menus.
4. •Questions you don't use. If an answer doesn't change anything, cut it.
5. •Ending on an empty screen. Onboarding should end with real content, not a blank list.
6. •No way back. Let users revisit answers and change them later in settings.
7. •Ignoring returning users. People who reinstall or switch phones shouldn't redo the whole quiz; offer "I already have an account" on the first screen.

Onboarding screen design checklist

• • The activation event is defined and tracked.
• • A new user reaches first value in about a minute or two, depending on the app.
• • The carousel, if any, has three screens or fewer and a visible Skip.
• • Every quiz question changes what the user sees.
• • Account creation comes after the first success where possible.
• • "I already have an account" is visible on the first screen.
• • Permissions are requested in context, each with a primer and a "Not now" option.
• • Headlines are under 8 words; body copy is one or two lines.
• • Buttons are full width, in thumb reach, and meet 44pt / 48dp minimums.
• • Progress is visible in quizzes and setup flows.
• • Empty states explain the screen and offer one primary action.
• • Each step fires an analytics event.

FAQ

How many onboarding screens should an app have?

As few as it takes to reach first value. For benefit carousels, three or fewer is a good rule; personalization flows can be longer if every question visibly shapes the experience. Measure step-by-step drop-off and cut screens that lose people without adding value.

Should onboarding include a sign-up screen?

Usually not at the start. Let people try the core feature first, then ask them to create an account to save their progress. Some apps, like banking or team tools, need an account up front, and should explain why.

When should I ask for notification permission?

After the user has experienced value and when a notification would clearly help, such as after scheduling a habit or finishing a first lesson. Show your own primer screen first and only trigger the system prompt if they agree.

What's the difference between onboarding and a tutorial?

A tutorial teaches how the interface works. Onboarding gets the user to their first success, which may include a short interactive task but focuses on outcomes rather than features.

How do I know if my onboarding is working?

Track your activation event and day 1 and day 7 retention alongside step completion. If people complete onboarding but don't activate or return, the flow isn't delivering value even though it looks smooth.

Design it with floow

Sketch your onboarding flow as a screen list, then generate it on floow.design and refine copy and layout through chat before exporting to Figma or code. Try: "Design a 7-screen iOS onboarding for a habit tracker: welcome with one illustration, goal picker with chips, suggested habits with toggles, schedule picker, home with first check-in tooltip, notification primer with Not now, and save-progress sign-in with Apple and Google. Friendly, coral and cream, 44pt tap targets."