appeeky/aso-skills

onboarding-optimization

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.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/appeeky/aso-skills --skill onboarding-optimization

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

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

按任务相关推荐

来自同一仓库

更多 Skills

全部 Skills
appeeky
社区

android-aso

When the user wants to optimize their Google Play Store listing — title, short description, full description, keywords, ratings, or Play Store-specific features. Use when the user mentions "Google Play", "Android", "Play Store", "Play Console", "short description", "full description indexed", "Google Play ASO", or wants Google Play-specific keyword, creative, or ratings strategy. For iOS App Store optimization, see aso-audit and metadata-optimization.

安装量
5
GitHub Stars
2197
最近更新
10月6日
appeeky
社区

localization

When the user wants to localize their App Store listing for international markets. Also use when the user mentions "localization", "translate my app", "international markets", "expand to new countries", "localize metadata", or "which countries should I target". For keyword research in specific markets, see keyword-research. For metadata writing, see metadata-optimization.

安装量
4
GitHub Stars
2197
最近更新
10月6日
appeeky
社区

review-management

When the user wants to analyze, respond to, or improve their app reviews and ratings. Also use when the user mentions "reviews", "ratings", "negative reviews", "how to get more reviews", "review response", or "my rating is dropping". For broader ASO audit, see aso-audit. For retention issues causing bad reviews, see retention-optimization.

安装量
4
GitHub Stars
2197
最近更新
10月6日
appeeky
社区

web-to-app-funnel

When the user wants to design or optimize the funnel that takes web visitors into installing and onboarding the app — including smart app banners, web-to-app deep links, deferred deep links, web onboarding (Stripe-paid web flow before app install), QR codes, "open in app" CTAs, and the trade-off between paying on web vs in-app. Use when the user mentions "web to app", "smart app banner", "Stripe before app", "web paywall before install", "Branch web SDK", "web funnel for app", "AppsFlyer OneLink

安装量
4
GitHub Stars
2197
最近更新
10月6日