# Onboarding — Mobile app

The first-run experience that orients a new user, collects necessary setup information, and delivers an early sense of the app value

Source: https://www.checklist.design/mobile/onboarding

## Items

### Steps
The number of steps in the onboarding flow, limited to what is genuinely required before the app can be used

_Tip: Steps that can be deferred without preventing the app from functioning on day one consistently belong later, not in onboarding_

### Progress indicator
A clear indication of how many steps remain and where in the sequence the user currently is

_Tip: Users who can see the end of onboarding are significantly less likely to abandon it than those who feel they are in a tunnel_

### Step navigation
A clear mechanism for advancing through steps e.g. a 'next' button or a horizontal swipe gesture

### Contextual permissions
Permissions surfaced at their contextually relevant moment within onboarding, rather than grouped at the start

_Tip: Grouping all permission requests at the beginning can lead to denials given lack of context_

### Skip option
A visible way to exit onboarding early and explore the app, with setup available to complete later

_Tip: Users who skip and explore freely often complete setup voluntarily once they understand the value_

### Personalisation step
One or two choices that make the app feel tailored from the start e.g. your name, interests, a key piece of information that applies to the product

### Keyboard handling
Views that adjust correctly when the keyboard appears, appropriate keyboard types per field, and Next advancing to the following input

## License for the Checklist Design collection

Checklist Design collection: https://github.com/Checklist-Design/skills
Snapshot: bfae71e507b1b7c03c12e0756402b60eb80f5d14 · Imported: 2026-11-12
Republished under the MIT License. Original checklist text belongs to Checklist Design.

MIT License

Copyright (c) 2026 Checklist Design

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.