Mobile onboarding and activation

Onboarding & Activation

Guide new and returning users to their first meaningful outcome as quickly and effortlessly as possible.

Core Onboarding Principles

• Value before friction: Let users experience core product value before demanding account creation, lengthy setup, or non-essential profile data whenever product constraints allow.
• Task-focused progression: Align every onboarding step directly with what the user needs to know or configure to achieve their first meaningful result.
• No decorative carousels: Avoid multi-slide marketing tours that users immediately skip and forget; teach through contextual, interactive steps or clear empty states.

Progressive Data Collection

• Ask now vs ask later: Separate inputs strictly required for initial activation from preferences or profile details that can be collected later in context.
• Contextual permission timing: Do not fire a barrage of OS permission dialogs on first launch. Request permissions at the moment the user triggers a feature that needs them, preceded by a clear rationale when helpful.
• Resumable setup: If onboarding or verification spans multiple steps (e.g. email/SMS verification, document upload, profile setup), save progress automatically so users who leave the app can resume where they left off.

First-Value & Empty-State Activation

• Observable activation: Name the user's first useful outcome and the evidence that it happened, such as a saved item they can reopen. Completing a tour or granting a permission alone does not establish product value.
• Actionable first screen: Ensure the screen a user lands on after onboarding has a clear primary action, helpful starter content or templates, and zero dead ends.
• Returning user paths: Distinguish first-time activation from returning sign-in, session expiry recovery, and device switching so returning users bypass first-time tours.

Handoff & Acceptance

• Deliver the path from entry to first value with required/deferrable inputs, permission-denied alternatives, saved checkpoints, and the destination after resume. If a permission is essential, explain the blocked capability and recovery action without repeatedly prompting.
• Exercise first use through the stated outcome, denied permissions, abandonment/relaunch, expired-session sign-in, and returning-user entry. Verify completed setup is retained for the correct account, pending verification is rechecked, and resumed users reach unfinished work without repeating completed steps or creating duplicates. Report which paths were observed and which remain design assumptions.