Mobile onboarding UI and flow examples
Compare required setup, personalization, progress and permissions across 40 reviewed screens from 7 apps. Read original notes on twelve selected frames, then try a separate web onboarding demo.
Notes reviewed · Source app versions are historical, not current-product guarantees.
Three focused onboarding studies
One recorded excerpt and two still-image sets. These observations describe supplied references, not conversion tests or accessibility certification. Notes remain readable without opening full-size media; the media keeps the existing account design allowance.
Duolingo: connect setup choices to a starting recommendation
Five selected moments from a January 2026 recording cover expectations, a language choice, daily effort, reminders and a proposed starting score.
Evidence limit: Recorded excerpt, not the complete onboarding journey. Other questions and purchase choices occur between these frames. The recording ends before the first lesson, so neither first value nor retention is established.
Opening…
Reference 1 · 0:09
Explain the setup effort
The introduction names seven questions and the first lesson as the destination; a single Continue action is visible.
Adapt it: Tell the person what setup is for and how much work to expect. Test whether every required answer changes the first session.
Reference 2 · 0:16
Make the consequential choice visible
French is highlighted in a language list beneath a progress bar. This answer determines the subject, rather than a cosmetic preference.
Adapt it: Ask for the choice that changes the task early. In your implementation, expose the selected state through a labelled control, not color alone.
Reference 3 · 0:53
Frame effort in understandable units
The daily goal is expressed in minutes, with ten selected. The action changes from Continue to a commitment-oriented label.
Adapt it: Make the consequence of the choice clear and keep revision available. A visible progress bar does not prove that the amount remaining is understood.
Reference 4 · 1:01
Separate the reminder explanation from permission
Reminder copy sits above a system-style permission preview with an arrow toward Allow. The bottom action asks for a practice reminder; this frame does not establish a live operating-system grant.
Adapt it: Explain the benefit in context, but keep app preferences and system permission as separate states. Test denial and continuation instead of assuming that a reminder choice grants notification access.
Reference 5 · 1:24
Reflect an earlier answer back
The recommendation refers to knowing a few words and proposes Score 10. It shows the result of an earlier proficiency answer.
Adapt it: Show how an answer changes the recommendation. Treat arriving at this screen separately from successfully completing a first lesson.
Structured: turn a planning promise into specific task details
Four September 2026 still references show a welcome, a wake-up time, task entry and a duration choice. They illustrate different setup decisions, not verified transitions.
Evidence limit: Still-image set, not a recorded journey. Display order is editorial. These images do not prove answer persistence, scheduling success, screen-reader behavior or what happens after Continue.
Opening…
Reference 1 · Still reference · Editorial display order
Keep new and returning paths distinct
The welcome screen has three introductory markers, Skip, a forward control and a separate returning-user login link.
Adapt it: Let the person bypass an introduction without confusing that choice with account sign-in. Markers can describe an introduction without measuring the entire setup.
Reference 2 · Still reference · Editorial display order
Give a time question visible context
The wake-up question shows 8 AM highlighted among neighboring times. A progress bar, back action and Skip remain visible.
Adapt it: Keep the selected value and its purpose together. Test time editing, large text and assistive technology in a real picker; the screenshot cannot establish those behaviors.
Reference 3 · Still reference · Editorial display order
Offer suggestions without removing custom input
A custom task field is shown above suggested activities such as answering emails and taking a walk.
Adapt it: Suggestions can help someone begin, but preserve their own task. Check the keyboard-open layout and retained input after going back.
Reference 4 · Still reference · Editorial display order
Put the duration beside the task
A Clean Up task card displays a fifteen-minute interval; the duration selector highlights 15m and offers a different-duration route.
Adapt it: Keep a preset's effect visible next to the task. Confirm that custom durations and changed start times are reflected in the final plan.
Notion Mail: distinguish identity, setup and mailbox access
Three September 2026 still references separate the account prerequisite, a setup waiting state and a Gmail connection explanation.
Evidence limit: Still-image set, not a recorded journey. These historical screens do not establish transition order, waiting time, the permission scopes granted, or current service availability.
Opening…
Reference 1 · Still reference · Editorial display order
Name the account prerequisite
The welcome screen explicitly names a Notion account before the Get started action, with terms and privacy copy below.
Adapt it: Explain an existing-account dependency before authentication. Do not treat accepting terms as permission to access another service.
Reference 2 · Still reference · Editorial display order
Recognize setup as its own state
A browser sheet shows a spinner and a setup message. Close, navigation and reload controls belong to that browser context.
Adapt it: Define a recoverable path for cancellation, timeouts and rejected requests. This still does not show how long the wait lasts or whether a retry succeeds.
Reference 3 · Still reference · Editorial display order
Explain the separate mailbox connection
A sheet names the Gmail address connection and offers its own continuation action over the welcome view.
Adapt it: Treat product identity and mailbox authorization as different decisions. Explain needed access and preserve a clear way to cancel or return.
Browse the other 28 reviewed onboarding references
These additional screens retain their source versions, original observations and app links. They are not additional complete recorded journeys.
Opening…
A practical onboarding design checklist
- Name the first useful task. Separate required account or data prerequisites from optional personalization; do not count a welcome or recommendation as a completed first task.
- Keep back, skip and returning-user routes understandable. Verify that answers survive revisiting a step.
- Explain what the progress indicator measures. Test conditional steps, long labels, a visible keyboard, larger text and narrow layouts.
- Separate an app preference from a device permission or provider authorization. Test denial, cancellation, timeout and retry without losing the main task.
Apple’s onboarding guidance recommends learning through interaction and postponing nonessential setup. The checklist above applies that principle to these references; it is editorial guidance, not measured performance.
Try an original three-step web onboarding example
Choose a goal and pace, go back to revise them, and optionally add a reminder preference. This demo is not one of the source apps: it makes no network requests, creates no account and asks for no device notification permission.
Practice studio · Original web demo
Step 1 of 3
What would you like to practice?
Mobile onboarding questions
What are mobile onboarding examples?
They show how an app introduces its purpose, collects necessary setup choices and helps someone begin a useful task. These examples include historical reference screens, original observations and design trade-offs; they are not ready-to-install copies of the source apps.
What is the difference between onboarding UI and an onboarding flow?
Onboarding UI is a particular screen or state. A flow also includes the transitions, decisions and alternate paths between states. The Duolingo example has selected timestamps from a recording. Structured and Notion Mail are still-image sets, so their display order does not establish working transitions.
How many onboarding examples are in this collection?
The collection has 40 reviewed screens from 7 apps. Twelve selected frames have additional notes in three focused studies. Source versions remain attached to the references; the new notes were reviewed on October 7, 2026.
Should onboarding show a progress indicator?
A progress indicator can communicate movement through required setup. A bar or a set of dots does not automatically explain the remaining work, especially when later branches change the number of steps. Test the indicator with clear step labels, back navigation and retained answers in your own implementation.
When should onboarding request notification permission?
Explain the task benefit when access is relevant, and distinguish a reminder preference from operating-system permission. A system-style prompt shown inside an explanatory screen is not evidence that access was granted. Test the actual grant, denial, deferred request and return-to-task states.
Can I reuse the interactive onboarding example?
The original React web demo is separate from the referenced apps. It keeps answers while going back and records an optional reminder preference; it does not create an account, call an API or request device notification access. Its source and license are linked from the Duolingo study; source downloads follow the site's access rules.







































