# Test mobile onboarding and the first launch, on a fresh install

> First launch is where new users decide. Each app run starts with fresh app data, so onboarding, prompts and the empty state are tested as a new user sees them.

By Jason Nguyen, Founder, Testsy. Published 2026-11-21. https://testsy.dev/blog/test-mobile-onboarding-and-first-launch/

## The screens your team never sees again

Everyone on the team installed the app months ago. Nobody sees the welcome screens, the first permission prompts or the empty home screen any more. New users see nothing else.

Onboarding bugs hit hardest because they come first. App reviews collected about onboarding show the pattern: a verification email that [never showed up](https://www.usercall.co/examples/app-review-examples-for-onboarding-issues), a phone number and an email both demanded before the app could be seen, a setup checklist that could not be finished without paying. Android's own guidance adds a quieter trap: after repeated denials the system [stops showing the permission dialog](https://developer.android.com/training/permissions/requesting), so a first-launch flow that assumes it can ask again leaves new users stuck.

## Every run is a first launch

Testsy app runs start with fresh app data each time, from [the app docs](https://testsy.dev/docs/apps/). There is no leftover session, no saved preference and no previous answer to a permission prompt. So onboarding is tested on every run, without uninstalling anything.

```text
Open the app. Go through the welcome screens with Next and finish with
Get started.
When the phone asks to send notifications, choose Don't Allow.
Sign up with this run's email address and confirm the code from the email.
Check the home screen explains how to create a first project and does
not show an error or an empty list without explanation.
Close the app and open it again; check the welcome screens are not
shown again.
```

The last line catches the onboarding that repeats on every launch because the "seen" flag was never saved.

## Prompts on the way

Permission prompts are drawn by the phone, not your app, which is why most tools cannot answer them. The tester can, and the answer can be part of the test ("choose Don't Allow"). We published a run that allows two and denies two: [Test permission prompts in a mobile app](https://testsy.dev/blog/test-permission-prompts-in-a-mobile-app/), which is the picture at the top of this page.

## Codes in onboarding

If sign-up sends a code, give the run its own mailbox (any plan) or phone number (paid plans): [Mailbox, phone number and endpoints](https://testsy.dev/docs/mailbox-phone-endpoints/). For an SMS arriving on the phone itself, see [Test SMS code sign-in on Android](https://testsy.dev/blog/test-sms-code-sign-in-on-android/).

## The empty state

A brand-new account has no data. Check what it sees:

- Does the first screen say what to do next?
- Do lists show a message instead of a spinner that never ends?
- Do totals show 0 instead of "NaN" or "undefined"?

## On the devices that matter

Run the onboarding test on the oldest OS version you support and on a tablet as well: prompts and layouts differ most there. See [One mobile test on every OS version](https://testsy.dev/blog/one-mobile-test-on-every-os-version/).

This post is part of [Mobile release testing: a guide for app teams](https://testsy.dev/blog/mobile-release-testing-for-app-teams/).
