Onboarding is the first run, and often the only run that decides whether someone stays. Most teams test the happy path once and move on. This list adds the cases that usually break: skips, going back, denied permissions, interruptions and users who come back. Each item has the expected result, a reason and how to check. Use a clean install every time.
The main path
- Complete onboarding as intended. Expected: ends on the first useful screen. Why: it is the baseline. How: install fresh and follow every step.
- Count the steps and the time. Expected: no step without a purpose. Why: each extra screen loses people. How: time it and ask of each screen what the user gains.
- Every screen has a clear primary action. Expected: one obvious button. Why: unclear screens stall. How: hand the phone to someone and watch.
Skip and back
- Skip each skippable step. Expected: the app still works and does not nag at once. Why: many users skip. How: skip all, then each individually.
- Skip everything, then use the app. Expected: nothing is missing that the app needs, such as a name or a setting. Why: skipped data can leave empty or broken screens. How: check the profile and home after skipping all.
- Go back from every step. Expected: previous input is kept, no crash. Why: users misread. How: Back button and swipe on each screen.
- Go back from the last step. Expected: sensible, not into a loop. Why: loops trap users. How: try on the last screen.
Permission prompts
- Prompts appear at a meaningful moment. Expected: with a reason shown first. Why: users deny requests they do not understand. How: note when each prompt shows and whether the context is clear.
- Deny each permission. Expected: onboarding continues; the app explains what is lost and how to enable it later. Why: denial is common. How: deny each one.
- Allow each permission, then use the feature. Expected: feature works. Why: confirms the positive path. How: allow and test.
- Change the permission in system settings later. Expected: the app reacts correctly on return. Why: users change their mind. How: switch it off in settings, return to the app.
Interruptions
- Close the app mid-onboarding and reopen. Expected: resumes at the right step or restarts cleanly. Why: calls and notifications interrupt. How: swipe the app away at each step.
- Phone call or alarm during a step. Expected: state kept. Why: it happens. How: trigger an alarm or call.
- Lose the network during onboarding. Expected: clear message and retry, no lost input. Why: signal drops. How: airplane mode at a step that needs the network.
- Rotate the device and use large text. Expected: buttons stay reachable. Why: small screens clip content. How: smallest device, large text.
Returning users
- Reopen after finishing onboarding. Expected: no onboarding again. Why: repeated onboarding annoys. How: close and reopen.
- Reinstall and log in with an existing account. Expected: skip or shorten onboarding where data exists. Why: returning users should not start over. How: reinstall and sign in.
- Update from an older version. Expected: no onboarding repeat, and new features are introduced gently if at all. Why: updates should not feel like a restart. How: install the previous build, finish onboarding, update.
- A second user on the same device. Expected: onboarding for the new account. Why: shared devices. How: log out and sign up as someone else.
Content
- Text and images fit different languages. Expected: no cut-off text. Why: German and others run longer. How: switch the system language. See also the questions to ask testers about your onboarding.
- No leftover placeholder text or test data. Expected: all final. Why: it is the first thing people read. How: read each screen.
Related
- Hub: Mobile app testing checklist hub
- Payment flow testing checklist
- Subscription cancellation and renewal testing checklist
The best onboarding test is a new person who has never seen your app. AppReviewX offers private, structured feedback from other developers; one feedback you write earns one credit. Start free.