App onboarding: what Apple's guidelines actually tell you to build
Teach through interactivity, prefer contextual tips over tours, keep tutorials optional and findable - Apple's Human Interface Guidelines on onboarding, turned into product decisions.
Most apps do not need an onboarding flow, and many that ship one would be better without it. Apple's Human Interface Guidelines say so almost directly: ideally people understand your app simply by experiencing it, and if onboarding is necessary, it should be fast, fun and optional. What follows is Apple's own guidance, checked 19 November 2026, translated into decisions for a product team.
What Apple actually recommends
- Onboarding is not part of launching. When it exists, it happens after launching completes - it is not the launch experience, and it should never gate it.
- Teach through interactivity. People grasp and retain more by performing the task than by viewing instructional material. Wherever possible, let people safely try the action, discover the feature or play the mechanic instead of watching a description of it.
- Prefer context-specific tips over a single flow. Tips delivered at the moment a task is relevant beat a front-loaded tour: people concentrate on one action at a time, and instructions land next to the interface area they describe. (Apple points developers to TipKit for this.)
- If a prerequisite flow is unavoidable, keep it brief and enjoyable. Teaching too much up front overwhelms people and they remember less of it, not more.
- Make separate tutorials optional and findable. If users can skip the tutorial at first launch, do not present it again on later launches - but keep it easy to find, for example in a help, account or settings area.
- Keep content about your experience, not the system. People enter onboarding to learn your app; they do not need to learn how to use the device.
The two delivery traps Apple warns about
Splash screens. If you include one, Apple says to display it just long enough to absorb at a glance without feeling delayed - a brief graphic, not a branding film.
Large downloads. People want to use the app immediately after first launch, whether they onboard or skip. Apple recommends shipping enough media and content in the package that nobody waits on a download before they can interact - a direct hit on the common pattern of an onboarding video wall followed by a 500 MB asset pull.
Design decisions this settles
- Default to no flow. Start from "the app explains itself"; add only what testing shows users actually miss.
- Measure completion honestly. If users skip or abandon your flow, the flow is the problem - Apple's guidance predicts exactly that response to long front-loaded teaching.
- Plan the re-entry path. Whatever can be skipped must be findable later; decide where it lives before launch, not after the support tickets arrive.
- Budget first-launch assets. "No waiting on downloads" is a packaging decision with real size trade-offs, made in the build system, not in the design file.
Sources
- Apple Human Interface Guidelines: Onboarding (checked 19 November 2026): https://developer.apple.com/design/human-interface-guidelines/onboarding
Drafted with AI assistance from this source. Apple's guidance is updated over time; check the current page when designing a flow for a new release.