PluginBench
Skill
Pass
Audit score 90

onboarding-optimization

appeeky/aso-skills

Optimize your app's first-run flow to maximize activation and reduce Day 1 drop-off.

What is onboarding-optimization?

This skill helps you identify your activation event (the first moment users get real value) and streamline the onboarding funnel to get users there as fast as possible. Use it when users are dropping off early, sign-up conversion is low, or you need to reduce permission-prompt friction.

  • Map and audit your current onboarding flow to identify friction-only screens
  • Score each screen by necessity, timing, value exchange, and cognitive load
  • Optimize permission-prompt timing and add pre-permission explanation screens to boost grant rates
  • Defer sign-up gates and long profile setup until after activation to reduce early drop-off
  • Apply value-first, personalization-first, or social-first onboarding patterns based on app type
  • Benchmark your funnel against industry standards and generate a revised flow with estimated impact

How to install onboarding-optimization

npx skills add https://github.com/appeeky/aso-skills --skill onboarding-optimization
Claude Code
Cursor
Windsurf
Cline

How to use onboarding-optimization

  1. 1.Identify your app's activation event (the first action that predicts long-term retention)
  2. 2.Map your current onboarding flow from app open to activation, listing every screen
  3. 3.Score each screen as Required, Value-adding, or Friction-only; flag drop-off points if known
  4. 4.Review permission-prompt timing against the provided rules and add pre-permission explanation screens where needed
  5. 5.Apply the recommended onboarding pattern (value-first, personalization-first, or social-first) for your app type
  6. 6.Generate a revised flow with estimated steps removed and time-to-activation reduction
  7. 7.Set up analytics to track activation funnel and measure lift from changes

Use cases

Good for
  • Fitness app: reduce the steps before first workout completion to increase Day 0 activation from 20% to 40%
  • Productivity app: move sign-up gate to post-activation so users experience task creation before committing an account
  • Social app: implement single-tap sign-in and friend suggestions to accelerate first post or comment
  • Finance app: defer email verification and ask only one personalization question to keep momentum
  • Meditation app: show a pre-permission screen explaining notification benefits before requesting push access
Who it's for
  • Mobile app product managers optimizing user acquisition funnels
  • Growth engineers reducing Day 1 drop-off and improving activation metrics
  • App developers designing first-run experiences for iOS or Android
  • Founders of early-stage apps trying to improve sign-up-to-activation conversion

onboarding-optimization FAQ

What's the difference between sign-up and activation?

Sign-up is creating an account; activation is the first time the user gets real value (e.g., completing a workout, creating a task, making a connection). Activation is what predicts long-term retention.

When should I ask for permissions like push notifications or location?

Ask after activation, not before. Always show a native-looking explanation screen first explaining the benefit. Users who understand the 'why' grant at 2–3× the rate.

Should I require sign-up before users try the app?

No. Defer sign-up to post-activation. Allowing guest mode or a try-before-sign-up flow typically converts 40–60% of guests to registered users, vs. 15–30% with a hard gate.

How many personalization questions should I ask in onboarding?

Maximum 3–5 questions. Each must visibly affect the experience, use visual selections not text inputs, and include a progress indicator.

Where should I place my paywall in onboarding?

Show value before the paywall. The strongest placement is post-activation on Day 1, when users have just felt the core value. Avoid showing it before activation.

Full instructions (SKILL.md)

Source of truth, from appeeky/aso-skills.


name: onboarding-optimization description: When the user wants to improve their app's onboarding experience, increase activation rate, reduce Day 1 drop-off, or optimize the first-run flow. Use when the user mentions "onboarding", "first-run", "activation", "tutorial", "day 1 retention", "new user flow", "permission prompts", "sign-up conversion", "onboarding funnel", or "users dropping off early". For overall retention strategy, see retention-optimization. For paywall placement, see monetization-strategy. metadata: version: 1.0.0

Onboarding Optimization

You optimize the first-run experience to maximize activation — the moment a new user completes the core action that predicts long-term retention.

The Activation Principle

Activation ≠ sign-up. Activation is the first time the user gets real value from your app. Identify it before anything else.

App TypeActivation Event
FitnessFirst workout completed
ProductivityFirst task or project created
SocialFirst connection made or content posted
FinanceFirst account linked or budget set
GamesFirst level or match completed
MeditationFirst session completed
Photo/VideoFirst photo edited or exported

Rule: Everything in onboarding should funnel toward that one activation event as fast as possible.

Initial Assessment

  1. Check for app-marketing-context.md
  2. Ask: What is your activation event?
  3. Ask: What % of new users reach it within 24 hours? (baseline)
  4. Ask: Where do users drop off? (which step, if known)
  5. Ask: How long does your current onboarding take? (steps, screens)
  6. Ask: Do you have Firebase/Mixpanel funnels set up?

Onboarding Audit Framework

Step 1 — Map the Current Flow

List every screen from app open to activation:

App open → [Screen 1] → [Screen 2] → ... → Activation event

Flag each screen: Required | Value-adding | Friction only

Remove or defer everything that is friction-only.

Step 2 — Score Each Screen

FactorQuestionScore
NecessityCan the user reach activation without this?0 = skip it
TimingIs this the right moment for this ask?
Value exchangeDoes the user understand why this benefits them?
Cognitive loadHow many decisions does this require?

Step 3 — Permission Prompt Timing

Permissions are the #1 drop-off point. Rules:

PermissionWhen to askNever ask
Push notificationsAfter activation, not beforeOn cold open
LocationWhen the feature needs itDuring sign-up
Camera/microphoneContextually, when usedBefore any value
ContactsWhen the social feature is usedIn onboarding
Tracking (ATT)After user is investedOn first open

The pre-permission screen: Always show a native-looking explanation screen before the system prompt. Users who understand the "why" grant at 2–3× the rate.

Step 4 — Sign-Up Friction

PatternImpactRecommendation
Required sign-up before valueHigh drop-offDefer to post-activation
Only email+passwordMedium drop-offAdd Sign in with Apple + Google
Long profile setupHigh drop-offAsk 1 question max, defer rest
Email verification requiredKills momentumDefer or make optional

Guest mode / try before sign-up: Allow users to experience the core value before requiring an account. Conversion from guest → registered is typically 40–60% vs. a hard gate at 15–30%.

Onboarding Patterns by App Type

Value-First (recommended for most apps)

Open → Core feature demo / interactive preview
     → Activation moment
     → "Save your progress" → Sign-up
     → Permission asks
     → Personalization

Personalization-First (works for health, fitness, AI apps)

Open → 3–5 personalization questions (show progress bar)
     → "Your plan is ready" reveal moment
     → Sign-up gate (invested now)
     → Activation

Social-First (social apps)

Open → Sign in with Apple/Google (single tap)
     → Find friends / follow suggestions
     → First feed with content
     → Activation (post, comment, react)

Funnel Benchmarks

StepBenchmarkPoor
App open → first interaction> 85%< 70%
Sign-up conversion> 60%< 40%
Push permission grant> 50%< 30%
Activation (D0)> 40%< 20%
Day 1 retention> 30%< 15%

Personalization Questions

If you include personalization, follow these rules:

  • Maximum 3–5 questions in onboarding
  • Each question must visibly affect the experience
  • Show a progress indicator (step 1 of 3)
  • Use visual selections, not text inputs
  • Never ask for data you won't use immediately

Paywall Placement in Onboarding

Rule: Show value before the paywall.

PlacementWorks When
Before activationAlmost never — user has no reference for value
At activationStrong — user just felt the value
Post-activation, D1Strongest for subscription apps
Contextual (feature gate)Good for feature-based paywall

See monetization-strategy for paywall design details.

Output Format

Onboarding Audit

Current flow:
  [Screen 1] — Required / friction
  [Screen 2] — Value-adding
  [Screen 3] — Required / friction
  ...
  [Activation event] — Step N

Drop-off analysis:
  Biggest drop: [screen] ([X]% exit rate if known)
  Estimated cause: [hypothesis]

Recommended changes:
1. [Remove / defer X] — Expected impact: [lift in activation]
2. [Reorder Y before Z] — Expected impact: [rationale]
3. [Add pre-permission screen for Z] — Expected impact: [grant rate improvement]

Revised flow:
  Open → [Screen] → [Screen] → Activation → Sign-up → Permissions
  Estimated steps removed: [N]
  Estimated time to activation: [Xs → Xs]

Permission Screen Copy Template

[Icon representing the permission]

[Benefit headline — what the user gets]
e.g., "Get notified when your goal is complete"

[One-line explanation]
e.g., "We'll only send you reminders you set — no spam."

[Allow button]     [Not now]

Related Skills

  • retention-optimization — Day 7/30 retention strategy
  • monetization-strategy — Paywall placement and trial design
  • ab-test-store-listing — Test onboarding variants
  • app-analytics — Set up activation funnel tracking
  • rating-prompt-strategy — When to ask for a rating post-activation