onboarding-optimization

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Onboarding Optimization

Onboarding 优化

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

你需要优化首次启动体验，以最大化Activation——即新用户完成能预测长期留存的核心操作的时刻。

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.

Activation ≠ 注册。 Activation是用户首次从你的应用中获得实际价值的时刻。请先明确这一核心事件。

应用类型	激活事件
健身类	完成首次训练
生产力类	创建首个任务或项目
社交类	建立首次连接或发布首条内容
金融类	关联首个账户或设置首个预算
游戏类	完成首个关卡或对局
冥想类	完成首次冥想 session
图片/视频类	完成首次图片编辑或导出

规则： Onboarding中的所有环节都应尽可能快速地引导用户完成这一核心激活事件。

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?

查看
```
app-marketing-context.md
```
文件
询问：你的激活事件是什么？
询问：有多少比例的新用户能在24小时内完成激活？（基准数据）
询问：用户在哪个环节流失？（若已知具体步骤）
询问：当前Onboarding流程需要多少步骤/页面？耗时多久？
询问：是否已设置Firebase/Mixpanel漏斗分析？

Onboarding Audit Framework

Onboarding 审计框架

Step 1 — Map the Current Flow

步骤1 — 梳理当前流程

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.

列出从应用启动到激活的每一个页面：

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

为每个页面标记：必填 | 增值 | 仅增加摩擦

移除或延迟所有仅增加摩擦的环节。

Step 2 — Score Each Screen

步骤2 — 为每个页面评分

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?

评估因素	问题	评分
必要性	用户无需此页面即可完成激活吗？	0分=可跳过
时机	此时请求该操作是否合适？
价值交换	用户是否理解这对他们的益处？
认知负荷	这需要用户做出多少决策？

Step 3 — Permission Prompt Timing

步骤3 — 权限请求时机

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.

权限请求是用户流失的首要原因。遵循以下规则：

权限类型	合适的请求时机	禁止的请求时机
推送通知	完成Activation后，而非之前	应用冷启动时
位置信息	当功能需要时	注册过程中
相机/麦克风	上下文触发（即使用时）	提供任何价值之前
通讯录	当使用社交功能时	Onboarding流程中
跟踪权限（ATT）	用户已投入使用后	首次启动时

权限请求前置说明页： 在系统权限弹窗前，务必展示一个原生风格的说明页面。理解“为什么需要权限”的用户，授权率会提升2-3倍。

Step 4 — Sign-Up Friction

步骤4 — 注册流程摩擦

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%.

模式	影响	建议
先注册再体验价值	高流失率	延迟至Activation后
仅支持邮箱+密码注册	中等流失率	添加“通过Apple/Google登录”选项
冗长的资料填写	高流失率	最多仅询问1个问题，其余延迟收集
强制邮箱验证	彻底打断用户节奏	延迟验证或设为可选

访客模式/先试后注册： 允许用户在要求注册前体验核心价值。访客转注册的转化率通常为40-60%，而强制注册的转化率仅为15-30%。

Onboarding Patterns by App Type

按应用类型划分的Onboarding模式

Value-First (recommended for most apps)

价值优先（适用于大多数应用）

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

启动应用 → 核心功能演示/交互式预览
     → 完成Activation
     → “保存你的进度” → 注册
     → 权限请求
     → 个性化设置

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

个性化优先（适用于健康、健身、AI类应用）

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

启动应用 → 3-5个个性化问题（展示进度条）
     → “你的专属方案已准备就绪”展示时刻
     → 注册环节（用户已投入）
     → 完成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)

启动应用 → 一键通过Apple/Google登录
     → 查找好友/关注推荐
     → 首次展示内容信息流
     → 完成Activation（发布、评论、互动）

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%

环节	基准值	较差值
应用启动 → 首次交互	> 85%	< 70%
注册转化率	> 60%	< 40%
推送通知授权率	> 50%	< 30%
首日Activation完成率	> 40%	< 20%
首日留存率	> 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

若包含个性化设置，请遵循以下规则：

Onboarding流程中最多包含3-5个问题
每个问题必须能显著影响用户体验
展示进度指示器（如“第1步/共3步”）
使用可视化选择，而非文本输入
绝不询问不会立即使用的数据

Paywall Placement in Onboarding

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.

规则： 先展示价值，再展示付费墙。

布局位置	适用场景
Activation前	几乎不适用——用户尚未感知到价值
Activation时刻	效果好——用户刚体验到价值
Activation后首日	对订阅类应用效果最佳
上下文触发（功能限制）	适用于基于功能的付费墙

如需付费墙设计细节，请查看

monetization-strategy

。

Output Format

输出格式

Onboarding Audit

Onboarding 审计报告

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]

当前流程：
  [页面1] — 必填/仅增加摩擦
  [页面2] — 增值
  [页面3] — 必填/仅增加摩擦
  ...
  [Activation事件] — 第N步

流失分析：
  最大流失点：[页面]（若已知退出率则标注[X]%）
  推测原因：[假设]

建议修改：
1. [移除/延迟X环节] — 预期影响：[Activation率提升]
2. [将Y环节调整至Z环节之前] — 预期影响：[理由]
3. [为Z权限添加前置说明页] — 预期影响：[授权率提升]

优化后流程：
  启动 → [页面] → [页面] → Activation → 注册 → 权限请求
  预计移除步骤数：[N]
  预计Activation耗时：[X秒 → X秒]

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]

[代表该权限的图标]

[利益导向标题——用户能获得什么]
例如：“当你完成目标时收到通知”

[一行说明]
例如：“我们仅发送你设置的提醒——无垃圾信息。”

[允许按钮]     [暂不允许]