onboarding-optimization
eronred/aso-skills
Optimize first-run experience to maximize activation and reduce Day 1 drop-off.
What is onboarding-optimization?
This skill helps you identify and optimize your app's activation event—the first moment a user gets real value—and streamline the onboarding flow to reach it faster. Use it when users mention onboarding friction, low activation rates, early drop-off, permission prompts, or sign-up conversion issues.
- Map and audit current onboarding flow to identify friction vs. value-adding screens
- Score each screen by necessity, timing, cognitive load, and value exchange
- Optimize permission prompt timing and pre-permission explanation screens to improve grant rates
- Reduce sign-up friction by deferring account creation, adding social login, and enabling guest mode
- Benchmark activation funnel against industry standards (40%+ D0 activation, 30%+ D1 retention)
- Design personalization questions (3–5 max) that visibly affect the user experience
How to install onboarding-optimization
npx skills add https://github.com/eronred/aso-skills --skill onboarding-optimizationHow to use onboarding-optimization
- 1.Identify your app's activation event (the first moment users get real value) using the provided app-type table
- 2.Map your current onboarding flow from app open to activation, flagging each screen as Required, Value-adding, or Friction-only
- 3.Score each screen using the audit framework (necessity, timing, value exchange, cognitive load)
- 4.Review permission prompt timing against the provided rules and add pre-permission explanation screens where needed
- 5.Analyze sign-up friction patterns (required sign-up before value, long profile setup, email verification) and defer non-critical asks to post-activation
- 6.Compare your funnel metrics (app open → first interaction, sign-up conversion, activation D0, Day 1 retention) against benchmarks
- 7.Generate a revised onboarding flow with estimated impact on activation rate and time-to-activation
Use cases
- Reduce Day 1 drop-off by removing unnecessary screens before the activation event
- Increase push notification grant rates from <30% to >50% using pre-permission explanation screens
- Defer sign-up until after activation to improve conversion from 15–30% to 40–60%
- Optimize permission timing (location, camera, contacts) to ask contextually when features are used
- Reorder onboarding screens to reach core value faster and reduce time-to-activation
- Product managers optimizing new user activation and retention
- Mobile app developers building or redesigning onboarding flows
- Growth teams analyzing funnel drop-off and permission grant rates
- Founders of fitness, productivity, social, finance, gaming, and media apps
onboarding-optimization FAQ
Activation is the first time a user gets real value from your app—not just creating an account. It predicts long-term retention. For example, in a fitness app, activation is completing the first workout, not signing up. Everything in onboarding should funnel toward that one event as fast as possible.
Ask permissions contextually when the feature is used, never on cold open. Always show a native-looking explanation screen before the system prompt—users who understand the 'why' grant at 2–3× the rate. Push notifications should be asked after activation, not before.
No. Allow users to experience core value in guest mode first. Conversion from guest → registered is typically 40–60%, vs. a hard sign-up gate at 15–30%. Defer account creation to post-activation when the user is invested.
Maximum 3–5 questions. Each must visibly affect the experience, use visual selections (not text inputs), and include a progress indicator. Never ask for data you won't use immediately.
Show value before the paywall. Placing it at activation (when the user just felt the value) or post-activation on Day 1 is strongest for subscription apps. Avoid showing a paywall before activation when the user has no reference for value.
Full instructions (SKILL.md)
Source of truth, from eronred/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 Type | Activation Event |
|---|---|
| Fitness | First workout completed |
| Productivity | First task or project created |
| Social | First connection made or content posted |
| Finance | First account linked or budget set |
| Games | First level or match completed |
| Meditation | First session completed |
| Photo/Video | First photo edited or exported |
Rule: Everything in onboarding should funnel toward that one activation event as fast as possible.
Initial Assessment
- Check for
app-marketing-context.md - Ask: What is your activation event?
- Ask: What % of new users reach it within 24 hours? (baseline)
- Ask: Where do users drop off? (which step, if known)
- Ask: How long does your current onboarding take? (steps, screens)
- 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
| Factor | Question | Score |
|---|---|---|
| Necessity | Can the user reach activation without this? | 0 = skip it |
| Timing | Is this the right moment for this ask? | |
| Value exchange | Does the user understand why this benefits them? | |
| Cognitive load | How many decisions does this require? |
Step 3 — Permission Prompt Timing
Permissions are the #1 drop-off point. Rules:
| Permission | When to ask | Never ask |
|---|---|---|
| Push notifications | After activation, not before | On cold open |
| Location | When the feature needs it | During sign-up |
| Camera/microphone | Contextually, when used | Before any value |
| Contacts | When the social feature is used | In onboarding |
| Tracking (ATT) | After user is invested | On 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
| Pattern | Impact | Recommendation |
|---|---|---|
| Required sign-up before value | High drop-off | Defer to post-activation |
| Only email+password | Medium drop-off | Add Sign in with Apple + Google |
| Long profile setup | High drop-off | Ask 1 question max, defer rest |
| Email verification required | Kills momentum | Defer 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
| Step | Benchmark | Poor |
|---|---|---|
| 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.
| Placement | Works When |
|---|---|
| Before activation | Almost never — user has no reference for value |
| At activation | Strong — user just felt the value |
| Post-activation, D1 | Strongest 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 strategymonetization-strategy— Paywall placement and trial designab-test-store-listing— Test onboarding variantsapp-analytics— Set up activation funnel trackingrating-prompt-strategy— When to ask for a rating post-activation
Related skills
More from eronred/aso-skills and the wider catalog.

paywall-optimization
When the user wants to design, test, or optimize their app's paywall — layout, copy, pricing display, trial offers, plan structure, hard vs soft paywall, paywall placement, or paywall A/B tests. Use when the user mentions "paywall", "paywall design", "paywall conversion", "trial-to-paid", "soft paywall", "hard paywall", "paywall A/B test", "paywall copy", "plan picker", "annual vs monthly display", "best paywall", "RevenueCat paywall", "Superwall", "Adapty", or "my paywall isn't converting". For overall pricing strategy and monetization model choice, see monetization-strategy. For trial nurture, dunning, and churn, see subscription-lifecycle. For where in the onboarding the paywall fires, see onboarding-optimization.

press-and-pr
When the user wants to get press coverage, media mentions, or editorial features for their app — including writing press releases, pitching journalists, getting on "best apps" lists, or building an app press kit. Use when the user mentions "press", "PR", "media coverage", "TechCrunch", "journalist", "press release", "app press kit", "get featured in media", "editorial coverage", "review from a blogger", or "app launch announcement". For Apple editorial featuring, see app-store-featured. For launch strategy, see app-launch.

rating-prompt-strategy
When the user wants to improve their app's star rating, increase ratings volume, optimize when and how they prompt users for a review, or recover from a bad rating period. Use when the user mentions "app rating", "star rating", "review prompt", "SKStoreReviewRequest", "In-App Review API", "ask for review", "low rating", "rating drop", "get more reviews", or "recover from 1-star". For responding to reviews, see review-management. For overall ASO health, see aso-audit.

referral-program
When the user wants to design, launch, or optimize an in-app referral / invite / share-to-earn program — including reward structure, mechanics, fraud prevention, deep link setup, and viral coefficient measurement. Use when the user mentions "referral program", "invite a friend", "refer and earn", "share to earn", "viral loop", "viral coefficient", "K-factor", "double-sided rewards", "give X get X", "referral rewards", "invite link", "share sheet", "Branch referrals", "in-app invites", or "how to make my app go viral". For deep link infrastructure that referrals depend on, see attribution-setup. For organic content-driven virality (UGC, creator), see creator-ugc-marketing.

retention-optimization
Diagnose and fix user churn with retention benchmarks, activation tactics, and engagement strategies.

review-management
Analyze, respond to, and improve app reviews to boost ratings and user trust.