Back to Details

indie-dev-skill

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Indie Dev Skills

独立开发者技能

Quick Start

快速开始

When invoked, return output in this exact section order:
  1. Assumptions
  2. Recommended Onboarding Flow
  3. Paywall Structure
  4. Pricing And Trial Setup
  5. Copy Variants
  6. Risks And Tradeoffs
  7. Next 7 Days Plan
Example output skeleton:
markdown
undefined
调用时，请严格按照以下章节顺序返回输出：
  1. 假设
  2. 推荐的Onboarding流程
  3. Paywall结构
  4. 定价与试用设置
  5. 文案变体
  6. 风险与权衡
  7. 未来7天计划
输出框架示例：
markdown
undefined

Assumptions

Assumptions

  • Region: US
  • Category: Mobile app
  • Region: US
  • Category: Mobile app

Recommended Onboarding Flow

Recommended Onboarding Flow

  • Screen 1: Problem framing
  • Screen 2: Personalization
  • Screen 3: Value reveal
  • Screen 1: Problem framing
  • Screen 2: Personalization
  • Screen 3: Value reveal

Paywall Structure

Paywall Structure

  • Value -> proof -> trial -> pricing
  • Value -> proof -> trial -> pricing

Pricing And Trial Setup

Pricing And Trial Setup

  • Default: annual plan with trial
  • Second option: weekly plan
  • Optional third option: monthly plan
  • Default: annual plan with trial
  • Second option: weekly plan
  • Optional third option: monthly plan

Copy Variants

Copy Variants

  • Headline A, Headline B
  • Headline A, Headline B

Risks And Tradeoffs

Risks And Tradeoffs

  • Potential annual friction in price-sensitive users
  • Potential annual friction in price-sensitive users

Next 7 Days Plan

Next 7 Days Plan

  • Day 1-2: Ship onboarding + paywall
  • Day 3-4: Refine copy and visuals
  • Day 5-7: Iterate based on qualitative feedback
undefined
  • Day 1-2: Ship onboarding + paywall
  • Day 3-4: Refine copy and visuals
  • Day 5-7: Iterate based on qualitative feedback
undefined

Overview

概述

Use this skill to build onboarding and paywall flows that improve conversion rate for indie apps with limited historical data. It combines onboarding guidance with paywall and pricing strategy, with the paywall shown at the end of onboarding after meaningful user interaction.
使用本技能为历史数据有限的独立应用搭建能提升转化率的Onboarding与Paywall流程。它将Onboarding指导与Paywall及定价策略相结合，在用户完成有意义的交互后，于Onboarding流程末尾展示Paywall。

Scope And Assumptions

适用范围与假设

  • Primary scope: mobile apps with subscription-led growth
  • Primary user: solo developers and small indie teams with limited time and analytics depth
  • If region is missing, assume US and label that assumption explicitly
  • If platform is missing, provide platform-agnostic guidance
  • Treat all numeric benchmarks as optional context; avoid numeric targets when no prior data exists
  • Utility-app benchmark references are directional; adapt recommendations by category
  • 核心适用范围：以订阅为增长模式的移动应用
  • 核心用户：时间有限、分析能力较弱的独立开发者与小型团队
  • 若未指定地区，默认假设为美国并明确标注
  • 若未指定平台，提供跨平台通用指导
  • 所有数值基准仅作为可选参考；若无历史数据，避免设定数值目标
  • 工具类应用的基准参考仅作方向指引，需根据应用类别调整建议

Indie Execution Mode

独立开发者执行模式

When the user has limited data or engineering bandwidth:
  • Prioritize the smallest shippable onboarding + paywall flow over complex optimization plans
  • Focus on a single primary conversion rate (paywall view -> trial or purchase)
  • Include a 1-week shipping plan with concrete steps
当用户数据有限或工程资源不足时：
  • 优先搭建最小可交付的Onboarding + Paywall流程，而非复杂的优化方案
  • 聚焦单一核心转化率指标（Paywall浏览 -> 试用启动或购买）
  • 包含1周可落地的实施计划，步骤具体明确

Onboarding Placement Rule

Onboarding放置规则

  • Require at least one meaningful user interaction before the paywall (input, selection, quiz, scan, or setup step)
  • Show the paywall at the end of onboarding, not before the user interacts
  • Ensure onboarding demonstrates user-specific value before pricing exposure
  • 在展示Paywall前，必须要求用户完成至少1次有意义的交互（输入、选择、测试、扫描或设置步骤）
  • Paywall需在Onboarding流程末尾展示，不得在用户交互前呈现
  • 在展示定价前，需通过Onboarding向用户展示个性化价值

Onboarding UX Rules

Onboarding UX规则

  • Prefer no dedicated onboarding when the core flow is already obvious
  • Use dedicated onboarding only when user data, personalization, or novel workflow explanation is required
  • Keep onboarding short (typically 3-5 screens) with one concept per step
  • Keep onboarding skippable with visible 
    Skip
    and a clear progress indicator
  • Avoid feature-promo carousels at first launch unless the feature is truly unfamiliar
  • Prefer contextual help and in-flow guidance over long tutorial slides
  • Defer visual theme customization until after users understand core app value
  • 若核心流程已足够直观，无需设置独立的Onboarding流程
  • 仅当需要收集用户数据、实现个性化或解释全新工作流时，才使用独立Onboarding
  • 保持Onboarding流程简短（通常3-5个页面），每页聚焦一个核心概念
  • 允许用户跳过Onboarding，需显示清晰的「Skip」按钮与进度指示器
  • 首次启动时，除非功能极为陌生，否则避免使用功能推广轮播图
  • 优先使用上下文帮助与流程内指导，而非冗长的教程幻灯片
  • 延迟视觉主题自定义，直到用户理解应用核心价值后再提供

Paywall Interaction Rules

Paywall交互规则

  • Use a close button only in the top-left corner
  • 仅在左上角设置关闭按钮

Input Checklist

输入检查清单

Capture these inputs before recommendations:
  • Region and currency
  • App category and target user
  • Current plans and price points
  • Trial setup (length, plan attachment, timing)
  • Funnel metrics only if available (use them to pick a single primary conversion rate)
  • Constraints (brand, legal copy requirements, launch timing)
If inputs are missing, default to:
  • Region: US
  • Currency: USD
  • Category: Mobile app
  • Trial: 7-14 days attached to annual
  • Team context: indie/solo, low analytics maturity
在给出建议前，需收集以下输入信息：
  • 地区与货币
  • 应用类别与目标用户
  • 当前套餐与定价
  • 试用设置（时长、关联套餐、展示时机）
  • 漏斗指标（若有，用于选定单一核心转化率）
  • 约束条件（品牌、文案合规要求、上线时间）
若输入信息缺失，默认采用以下设置：
  • 地区：美国
  • 货币：美元（USD）
  • 类别：移动应用
  • 试用：7-14天，与年度套餐绑定
  • 团队背景：独立/单人开发者，分析能力较弱

Disallowed Outputs

禁止输出内容

Never include:
  • Legal, tax, or compliance advice
  • Backend billing architecture or server implementation plans
  • SDK-specific setup instructions or tool walkthroughs
  • App architecture mandates (MVVM/MVC or project-structure prescriptions)
  • Guaranteed outcome claims from benchmark data
绝对不能包含：
  • 法律、税务或合规建议
  • 后端计费架构或服务器实施计划
  • SDK特定设置说明或工具操作指南
  • 应用架构强制要求（如MVVM/MVC或项目结构规定）
  • 基于基准数据的结果保证声明

Workflow Decision Tree

工作流决策树

1) Clarify context

1) 明确上下文

  • App category, user problem, target regions
  • Current pricing, trial setup, and metrics (if available)
  • If data is missing, state assumptions before making recommendations
  • 应用类别、用户痛点、目标地区
  • 当前定价、试用设置与指标（若有）
  • 若数据缺失，在给出建议前明确说明假设条件

2) Build onboarding flow

2) 搭建Onboarding流程

  • Identify user problem
  • Personalize quickly (scan, quiz, or setup)
  • Demonstrate value before pricing
  • Include at least one interaction step before presenting the paywall
  • Keep each step focused on one job and ensure skip/progress affordances are visible
  • 明确用户痛点
  • 快速实现个性化（扫描、测试或设置）
  • 在展示定价前先呈现价值
  • 在展示Paywall前至少包含1个交互步骤
  • 每个步骤聚焦一个核心目标，确保跳过/进度提示清晰可见

3) Design paywall

3) 设计Paywall

  • Multi-screen value -> proof -> trial -> pricing
  • Annual plan highlighted and preselected
  • Equivalent monthly cost shown for annual
  • 采用多页面流程：价值展示 -> 价值验证 -> 试用 -> 定价
  • 突出并默认选中年度套餐
  • 显示年度套餐对应的等效月付成本

4) Validate against defaults

4) 与默认设置对齐

  • Trial attached to annual plan, 7–14 days
  • “Cancel anytime” visible
  • Paywall appears at the end of onboarding after interaction
  • 试用与年度套餐绑定，时长7-14天
  • 显示「随时取消」提示
  • Paywall在用户完成交互后的Onboarding流程末尾展示

5) Plan a simple iteration loop

5) 规划简单迭代循环

  • Ship, observe qualitative feedback, and iterate on copy and layout
  • 上线流程，收集定性反馈，迭代文案与布局

Decision Policy (Conflict Arbitration)

决策政策（冲突仲裁）

  • Start with Annual Default when:
  • No strong evidence of high price sensitivity
  • Category supports longer commitment (productivity, health, education, pro utility)
  • Use Weekly Entry then Upsell when:
  • Early data shows annual trial-start friction
  • Audience is high-churn, low-commitment, or highly price-sensitive
  • Resolution rule:
  • If guidance conflicts, prioritize current product metrics over static defaults
  • If metrics are unavailable, provide both variants and mark one as primary with rationale
  • 当满足以下条件时，优先采用「年度套餐+试用」默认方案：
    • 无明显证据表明用户对价格高度敏感
    • 应用类别支持长期订阅（生产力、健康、教育、专业工具类）
  • 当满足以下条件时，优先采用「周付入门+年度升级」方案：
    • 早期数据显示年度套餐试用启动存在阻力
    • 目标用户流失率高、承诺意愿低或对价格高度敏感
  • 冲突解决规则：
    • 若指导建议存在冲突，优先基于当前产品指标而非静态默认设置
    • 若无可用指标，提供两种变体方案，并标注其中一种为首选方案并说明理由

Starter Defaults (US Mobile Apps, unless user overrides)

初始默认设置（美国移动应用，用户可覆盖）

  • Currency scope: USD only; localize prices before applying outside US
  • Primary default: Annual $29.99 with 7-14 day trial ("Best Value", default selected, "Cancel anytime" visible)
  • Second option: Weekly $4.99
  • Do not include a monthly plan as the default or primary option
  • Recommended first test variant: weekly-first entry with annual upsell
  • 货币范围：仅美元；在美国以外地区使用时需本地化定价
  • 核心默认方案：年度套餐29.99美元，附带7-14天试用（标注「最佳价值」，默认选中，显示「随时取消」）
  • 第二选项：周付4.99美元
  • 默认不包含月付套餐作为核心选项
  • 推荐首次测试变体：周付入门+年度升级

Conflict Matrix

冲突矩阵

  • Annual + trial default
    : best for conversion when users value longer commitment and trust the product
  • Weekly second option
    : best for conversion when price sensitivity or commitment friction is high
  • Tie-breaker
    : pick the option most likely to improve paywall conversion rate based on user context
  • 「年度套餐+试用默认方案」：当用户重视长期承诺且信任产品时，对转化最有利
  • 「周付第二选项」：当用户对价格敏感或承诺阻力大时，对转化最有利
  • 平局决胜：基于用户上下文选择最可能提升Paywall转化率的方案

Deliverables

交付成果

Provide all or subset as requested:
  • Onboarding screen sequence with goals
  • Interaction checkpoint before paywall
  • Paywall flow outline (screen-by-screen)
  • UI design tips for onboarding and paywall layout
  • Pricing table and selection hierarchy
  • Copy blocks (headline, subhead, benefits, CTA, disclaimers)
  • Loss-aversion messaging variants
  • Lightweight implementation plan (what to ship this week)
可根据需求提供以下全部或部分内容：
  • 带目标说明的Onboarding页面序列
  • Paywall展示前的交互检查点
  • Paywall流程大纲（逐页面）
  • Onboarding与Paywall布局的UI设计建议
  • 定价表与选项优先级
  • 文案模块（标题、副标题、权益、CTA、免责声明）
  • 损失厌恶文案变体
  • 轻量实施计划（本周需完成的上线内容）

Minimum Event List (Optional)

最小事件列表（可选）

If the user asks for instrumentation, keep it minimal:
  • onboarding_started
  • onboarding_completed
  • paywall_viewed
  • trial_started
  • subscription_purchased
  • trial_canceled
若用户询问埋点建议，仅提供以下核心事件：
  • onboarding_started
  • onboarding_completed
  • paywall_viewed
  • trial_started
  • subscription_purchased
  • trial_canceled

Required Response Template

强制响应模板

Return outputs using these sections in order:
  1. Assumptions
  2. Recommended Onboarding Flow
  3. Paywall Structure
  4. Pricing And Trial Setup
  5. Copy Variants
  6. Risks And Tradeoffs
  7. Next 7 Days Plan
严格按照以下章节顺序返回输出：
  1. 假设
  2. 推荐的Onboarding流程
  3. Paywall结构
  4. 定价与试用设置
  5. 文案变体
  6. 风险与权衡
  7. 未来7天计划

References

参考资料

  • references/onboarding-playbook.md
    - Onboarding rules, benchmarks, and tests
  • references/paywall-playbook.md
    - Pricing rules, trial strategy, benchmarks, and tests
  • references/subscription-apps-highlights.md
    - Report highlights on trial timing, conversion, and paywall placement
  • references/mobile-onboarding-usability-guidance.md
    - Usability-first guidance on when onboarding is justified and how to keep it minimal
  • references/mobile-onboarding-paywall-design-tips.md
    - Practical mobile UI design tips for onboarding and paywall presentation
  • references/in-app-subscriptions-highlights.md
    - Pricing mix, regional trends, and paywall tactics
  • references/metric-definitions.md
    - Funnel metric definitions and calculation boundaries
  • references/onboarding-playbook.md
    - Onboarding规则、基准与测试指南
  • references/paywall-playbook.md
    - 定价规则、试用策略、基准与测试指南
  • references/subscription-apps-highlights.md
    - 关于试用时机、转化与Paywall放置的报告要点
  • references/mobile-onboarding-usability-guidance.md
    - 以可用性为核心的指导：何时需要Onboarding及如何简化流程
  • references/mobile-onboarding-paywall-design-tips.md
    - 移动应用Onboarding与Paywall设计的实用UI建议
  • references/in-app-subscriptions-highlights.md
    - 定价组合、地区趋势与Paywall策略
  • references/metric-definitions.md
    - 漏斗指标定义与计算边界

Philosophy

设计理念

  • The decision to subscribe happens before the paywall
  • Optimize for Day-0 trial starts and annual adoption
  • Prefer clarity and value-first messaging over gimmicks
  • 用户的订阅决策在看到Paywall前就已形成
  • 优化首日试用启动率与年度套餐 adoption
  • 优先采用清晰、价值导向的文案，而非噱头