Onboarding

Patterns
View as Markdown
On this page3 sections

Best practices

Teach through interactivity.

Consider providing a collection of context-specific tips instead of a single onboarding flow.

If you need to present a prerequisite onboarding flow, design a brief, enjoyable experience that doesn’t require people to memorize a lot of information.

If it makes sense to offer a separate tutorial, consider making it optional.

Keep onboarding content focused on the experience you provide.

Additional content

Briefly display a splash screen if necessary.

Don’t let large downloads hinder onboarding.

Avoid displaying licensing details within your onboarding flow.

Additional requests

Postpone nonessential setup flows or customization steps.

If your app or game needs access to private data or resources before it can function, consider integrating the permission request into your onboarding flow.

Prefer letting people experience your app or game before prompting them for ratings or purchases.


For the complete guidance, including worked examples and illustrations, see the canonical page: https://developer.apple.com/design/human-interface-guidelines/onboarding

Apple HIG text and imagery are © Apple Inc. This page is a structured index of Apple’s canonical documentation (snapshot 2025-02-02), provided for quick reference and AI-agent consumption — it isn’t affiliated with or endorsed by Apple. Read the original at developer.apple.com (opens in new tab).

Get HIG guidance in your AI

Install HIG Doctor and get expert Apple design guidance directly in Claude Code.

npx skills add raintree-technology/hig-doctor
Email updates aren't configured on this deployment yet. Follow the GitHub repo (opens in new tab) for updates.