app onboarding best practices come down to one job: get a new user to their first real result, fast. show value before you ask for an account, ask only questions that change the first experience, request permissions when a feature needs them, and make the first screen deliver what the ad promised. then measure activation and day 1 retention.
the first session decides whether there is a second one. for the numbers behind that, see app retention.
What is the job of app onboarding?
the job of onboarding is to shorten time to first value: the minutes between opening the app and getting the result the user came for. it is not a tour of features. every screen should either deliver part of that result or collect something that makes the result better. anything else is friction.
define first value as one trackable event, such as “first photo edited”. that is your activation metric, the one i put first in app growth metrics that matter. Apple’s onboarding guidance asks for a flow that is “fast, fun, and optional”.
Onboarding flow patterns that work
most good onboarding flows combine four patterns: value first, progressive signup, a short personalization quiz and a deliberate paywall position. you do not need all four. choose based on how quickly your core action can run without data from the user, and whether you sell a subscription. here is each one, described in words.
Value-first onboarding
the user does the core action on the first screen, before any signup. a photo app opens to “pick a photo”. a language app starts a one minute lesson. Apple’s guidance recommends teaching through interactivity rather than instructional screens, and offering small context-specific tips near the feature instead of one long tour up front.
Progressive signup
ask for an account only when there is something worth saving: a result, a streak, a plan. guest mode first, then “save your progress” after the first win. Apple’s App Review Guidelines (5.1.1) say an app without significant account-based features should let people use it without a login.
Personalization quiz
two to five questions that visibly change what the user sees next: goal, level, time available. the rule is simple: if an answer does not change the first plan or screen, delete the question. a quiz also works as a commitment step, because the user has put something in before they see the result.
Paywall placement
RevenueCat’s State of Subscription Apps 2026 found that in most categories 80 to 89% of trials start on install day, so the onboarding paywall matters. in the same data, hard paywalls had a median day 35 download-to-paid of 10.7% against 2.1% for freemium. a hard paywall only works if the taste of value before it is strong, so test both. whichever you choose, Apple’s guidelines (3.1.2) ask you to clearly describe what the user gets before asking them to subscribe.
Permission priming: the official rules
permission priming means explaining why you need access before the system prompt appears. both platforms allow it but set rules. ask in context when the user starts the feature that needs it, explain the benefit plainly, never block the app if they say no, and on iOS never dress your explainer up as the system prompt.
- notifications on Android: from Android 13, notifications are off by default for new installs. Google recommends letting people get familiar with the app first and triggering the prompt from an action, such as tapping a bell icon.
- denials on Android: if the user taps deny for the same permission more than once, Android treats it as permanent and stops showing the dialog, per the runtime permissions guide. ask too early and you can lose the feature for good.
- notifications on iOS: the system prompts only the first time you request authorization. Apple’s notification guide suggests asking in context, such as after someone schedules their first task, or using provisional authorization to deliver quietly first.
- explainer screens on iOS: Apple’s privacy guidelines say a custom screen shown before the alert should have one button, titled with a word like “Continue” or “Next” rather than “Allow”, and no way to leave without seeing the alert.
- tracking on iOS: if you share data with other companies to track people across apps and websites, you must use App Tracking Transparency and include a usage description that explains why.
- when people say no: Google asks apps to degrade gracefully and not nag, and Apple’s guidelines say apps must not manipulate, trick or force people to consent to unnecessary data access.
Match the ad promise to the first screen
the fastest onboarding win often sits outside the app: make the first screen deliver the exact promise of the ad and store page that brought the user. if a creative promises, as an illustrative example, “fix your essay in 30 seconds”, the first screen should be an essay box, not a welcome carousel. a mismatch reads as bait.
this is standard practice in how i run paid acquisition. with 150+ ad creatives tested every month, winners are judged on whether people from that ad finish onboarding and come back, not on CPI alone. lining up the first screen with each winning ad’s promise lowered effective CAC, because the same spend produced more users who returned. the testing process is in app creative testing, and the store step in between is in App Store screenshots.
How to audit your onboarding flow, step by step
audit your flow the way a new user meets it: from the ad, through the store page, to the first result. do it on a fresh install with a new account, on both platforms, and time it. write down every screen, every question and every prompt, then ask what each one does for the first result.
- install fresh from a real ad. delete the app, tap a live ad, and screen record through to the first result.
- time it. note the seconds to first value and count the taps. that is your baseline.
- list every screen. mark each one: delivers value, improves the result, or neither. cut or move the “neither” screens.
- check the promise. does the first screen move toward what the ad and store page said? if not, change the screen or the ad.
- check every permission prompt. is it triggered by a feature the user just chose, and does the explainer follow the rules above?
- check signup timing. can someone reach first value before creating an account?
- check the paywall. has the user seen value before it, and are the price and what they get stated plainly?
- read your funnel. in your analytics, find the screen where the biggest share of new users drop. that is your first fix.
How to test onboarding changes
test one change at a time on new users only, and judge it on activation and day 1 retention, not screen completion. a shorter flow can raise completion while lowering retention if you removed the step that made the product feel personal. run each test across at least a full week so weekday patterns even out.
- split new installs between the current flow and one variant, using your analytics or remote config tool. never switch existing users mid-flow.
- pick the metric before the test: activation rate first, then day 1 and day 7 retention, then trial starts if you sell subscriptions.
- wait for enough users. as an illustrative rule of thumb, small differences need thousands of installs per variant before you trust them. with a few hundred installs a week, test big changes, not button colours.
- keep a log. date, change, result and decision, so you never re-test the same idea by accident.
Example onboarding flows for three app types
these are illustrative flows i sketched for this page, not copies of real apps. each uses the patterns above in order: value first, a short quiz where it earns its place, signup after the first win and permissions in context. adapt the order to your own first value event, then test it.
habit or fitness app (illustrative)
- one question: what do you want to build? three goals to pick from.
- two more questions: level and minutes per day. the plan on the next screen changes with each answer.
- the first session starts straight away: a five minute routine.
- finish screen: “save your plan and streak”, with sign in options.
- the reminder prompt appears only after they pick a time for tomorrow’s session.
AI photo editor (illustrative)
- opens to “pick a photo”, using the system photo picker instead of full library access where possible, as Apple’s guidelines suggest.
- one tap applies the edit the ad showed, with before and after on screen.
- export free with a small watermark, or start a trial to remove it. the paywall states exactly what the trial includes.
- an account is requested only when they want edits synced across devices.
budgeting app (illustrative)
- value first without a bank link: enter this month’s income and three biggest costs.
- show a simple “safe to spend” number straight away.
- offer to connect accounts for automatic tracking, with a plain explanation of what is read and why.
- account creation to save the budget, and a notification prompt only when they turn on a bill reminder.
for how onboarding fits the whole job, read what an AI app growth marketer does.
Frequently asked questions
What are app onboarding best practices?
get people to one meaningful result as fast as possible. show value before asking for an account, ask only questions that change the first experience, request permissions when a feature needs them, and make sure the first screen matches what the ad or store page promised. then measure activation and day 1 retention by cohort.
How many onboarding screens should an app have?
there is no correct number. keep a screen only if it changes what the user sees next or gets them closer to their first result. a short quiz that personalises the first plan can earn its place, while a carousel of feature slides usually does not. test removing screens and watch activation and day 1 retention.
When should an app ask for notification permission?
ask when the user does something that makes notifications useful, such as setting a reminder or following a topic. Apple and Google both advise asking in context rather than at first launch. on Android 13 and later, new installs start with notifications off, and on iOS the system shows the prompt only once.
Want this applied to your app? Send me your numbers.
tell me about your app, what you are testing and where it is stuck. i'll reply myself with what i would try next. no pitch, not a sales call.