App Onboarding Checklist: 6 Areas to Check, With Real Test Results

An app onboarding checklist covers six things: the first screen, flow length, personalization, permission requests, where the paywall sits, and how you measure it all.

In tests from our database, the biggest gains came from asking better questions and moving the paywall earlier, not from cutting screens.

Work through the list in order, and A/B test any change you can't defend with data.

Every test cited below comes from the LiftArchive onboarding test library.

Most are vendor-reported case studies from RevenueCat, Superwall or Apphud, so read the numbers as directional, not guaranteed.

1. First screen: make the promise in one glance

The first screen decides whether people keep tapping.

It should say what the app does for them and give one obvious next step.

• One outcome, stated plainly. "Learn sign language in 5 minutes a day" beats a logo and a tagline.
• One primary button. "Get started" or "Continue". Put "Log in" as a smaller text link for returning users.
• No forced sign-up before value. Apple's App Review Guideline 5.1.1(v) says that if your app doesn't include significant account-based features, you must let people use it without a login.
• Match the ad or store page. If someone installed from a screenshot about budgeting, the first screen should talk about budgeting. See our custom product pages guide for matching store pages to campaigns.
• Consider starting on the web. Teaching.com moved onboarding to the web before download and reported about +50% conversion to trial and about +30% conversion to paid. More on that in our web-to-app guide.

2. Length: don't cut screens by reflex

"Shorter is better" is the most common onboarding advice, and our database doesn't back it up.

Screens that build intent tend to pay for themselves.

• Test a longer flow before you test a shorter one. Lose It! added more questions to onboarding and saw trial start rate up by double digits.
• Test several flows at once if you have the traffic. AEZAKMI Group tested six onboarding flows for an LED controller app; the winner moved conversion from 0.8% to 1.29% (+61%), with ARPU from $0.12 to $0.14 (+16%).
• Every screen needs a job. It should collect an answer you use later, show the product working, or build trust. Cut screens that only repeat feature lists.
• Show progress. A progress bar tells people the flow ends, which matters more as it gets longer.
• Find the drop-off screen, not the average. Track completion per screen so you know which one loses people.

3. Personalization: ask questions you actually use

Quizzes work when the answers change what the user sees next.

Our onboarding quizzes element page collects every test on this pattern.

• Start with goals. Applica rebuilt ASL Bloom's onboarding around the user's goal, with a two-screen paywall, and reported +15% trial conversion, +12% ARPU and +18% 30-day retention. That was a bundled change, so no single screen gets the credit.
• Base questions on research. Applica also rebuilt Five Minute Journal's onboarding from jobs-to-be-done interviews and reported +20% ARPU, about +10% trial starts and +14% trial conversions.
• Play answers back. After the quiz, show a summary or plan built from the answers ("Your 4-week plan for..."). That screen is what makes the questions feel worth it.
• Use the answers downstream. Feed them into the paywall copy, the first session and your push messages. A quiz whose data goes nowhere is just a longer flow.
• Keep questions easy. Single tap, multiple choice, no typing unless it's essential.

4. Permissions: ask in context, explain first

Both platforms limit how many times you can ask.

On iOS, Apple's notification docs say the system prompts only the first time your app requests authorization.

On Android 11 and up, if a user taps Deny more than once, the system dialog no longer appears.

• Don't fire every prompt on first launch. Apple suggests asking in context, for example after someone schedules a first task. Google gives similar advice for the Android 13 notification permission: let users get to know the app, then ask after an action like tapping an alert bell.
• Use a primer screen. A screen before the system dialog that says what the user gets ("We'll remind you at 8 pm"). See our permission primers page.
• Be honest on the ATT primer. Apple's user privacy FAQ allows an explanation before the tracking prompt as long as you are transparent about how the data is used. Guideline 5.1.2(i) bans requiring tracking, push or location to use the app, or rewarding people for enabling them. More in our ATT guide.
• Only ask for what the feature needs. Guideline 5.1.1(iv) bans tricking or forcing people into unnecessary data access, and asks for alternatives where possible, such as typing an address if Location is declined.
• Consider provisional push on iOS. With provisional authorization, notifications arrive quietly in Notification Center with Keep and Turn Off buttons, and there's no up-front prompt.
• Benchmark your rates. Compare yours with our push opt-in rate benchmarks.

5. Paywall position: test showing it earlier

Placement is the strongest lever in our onboarding data.

Most people who will ever see your paywall see it during onboarding, so a paywall that only shows up later reaches far fewer users.

• Put a paywall inside or at the end of onboarding. Greg added a paywall to onboarding for everyone and reported about +400% trial sign-ups, with sign-up-to-trial going from 3% to 15%. That was bundled with feature gating.
• Test it at the very start. Rootd moved the paywall to the start of onboarding and reported revenue 5x. That was a before-after comparison, not a controlled test, so seasonality and other changes may play a part.
• Combine early placement with context. In a three-way test written up by Rosie Hoggmascall, trial opt-in was 2% (A) vs 8% (B) vs 15% (C); the winner showed the paywall before onboarding plus a carousel.
• Try a second paywall. Rizz App used two paywalls in onboarding and reported +10% onboarding conversion and +10% trial conversion.
• Watch refunds and trial-to-paid, not just trial starts. BoldVoice's paywall with no close button got more trial starts, but refunds rose by more than the gain.
• Check the paywall itself. Placement can't fix a weak offer. Run our paywall checklist and read the paywall timing tests.

6. Measurement: track the whole funnel

Onboarding changes often move one number up and another down. Set up tracking before you ship anything.

• Log every screen. Track a view event and a completion event per screen, so you can build a step-by-step drop-off funnel.
• Track past the trial start. Measure trial-to-paid, refunds, ARPU and day-30 retention, not just onboarding completion. Compare yours to our trial conversion benchmarks.
• Size tests before you run them. Small apps need large lifts to reach significance. Use the A/B test sample size calculator before you launch.
• Prefer A/B tests over before-after. Before-after results, like Rootd's, are easier to run but mix in seasonality and ad changes.
• Change one thing when you can. Bundled redesigns, like ASL Bloom's, can win big, but you won't know which part did the work.
• Segment by platform and source. iOS and Android users, and paid and organic installs, often react differently to the same flow.

The checklist at a glance

For the full picture of how these pieces fit together, read our app onboarding guide.