app-store-opportunity-research
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChinesePrerequisites
前置条件
- Browser tools for App Store browsing and research
- Web search for Reddit, Google Trends, and indie revenue research
- No API keys required — all research is done through browser and web search
- 浏览器工具：用于浏览和调研App Store
- 网络搜索：用于Reddit、Google Trends和独立开发者收益调研
- 无需API密钥——所有调研均通过浏览器和网络搜索完成
Pipeline Overview
流程概览
1. Define Category & Goals
2. App Store Charts Research
3. Community & Demand Research
4. Competitor Deep-Dive
5. Revenue Deep-Dive
6. Gap Analysis
7. Score & Rank
8. Top 3 Report
9. Quick Validation (optional)
10. MVP PRD1. 定义品类与目标
2. App Store榜单调研
3. 社区与需求调研
4. 竞品深度分析
5. 收益深度分析
6. 缺口分析
7. 评分与排名
8. 前三机会报告
9. 快速验证（可选）
10. 撰写MVP PRDStep 1: Define the Category & Goals
步骤1：定义品类与目标
Ask the user what space they want to explore. Help them narrow down:
- Too broad: "Health apps" (thousands of competitors)
- Good: "Sleep + anxiety apps for consumers" (specific intersection)
- Good: "Habit tracking for fitness beginners" (audience + niche)
- Good: "AI-powered journaling apps" (tech angle + category)
Key questions to ask:
- What category or problem space interests you?
- Consumer or B2B? (Consumer is easier to validate quickly)
- Any budget constraints? (No-AI = cheaper to build, AI = higher ceiling)
- Target revenue? ($1K/mo side project vs $10K/mo business vs $50K+/mo full-time replacement)
- What's your timeline? (2-4 week MVP vs 2-3 month polished launch)
- Do you have domain expertise or personal pain in this area? (Strongest apps come from scratching your own itch)
询问用户想要探索的领域。帮助他们缩小范围：
- 过于宽泛：“健康应用”（数千个竞品）
- 合适：“面向消费者的睡眠+焦虑应用”（明确的交叉领域）
- 合适：“面向健身新手的习惯追踪应用”（受众+细分领域）
- 合适：“AI驱动的日记应用”（技术角度+品类）
关键问题：
- 你感兴趣的品类或问题领域是什么？
- 面向消费者还是B2B？（消费者领域更容易快速验证）
- 有预算限制吗？（无AI功能=开发成本更低，AI功能=收益上限更高）
- 目标收益是多少？（每月1000美元的副业 vs 每月10000美元的业务 vs 每月50000美元以上的全职收入替代）
- 你的时间规划是怎样的？（2-4周的MVP vs 2-3个月的完整版本发布）
- 你在该领域有专业知识或个人痛点吗？（最成功的应用往往源于解决自身需求）
Step 2: App Store Charts Research
步骤2：App Store榜单调研
Browse the iOS App Store charts to map the competitive landscape.
浏览iOS App Store榜单，梳理竞争格局。
Chart URLs
榜单URL
Navigate to:
https://apps.apple.com/us/charts/iphone/{category-slug}/{category-id}Apps:
| Category | Path |
|---|---|
| Books | |
| Business | |
| Education | |
| Entertainment | |
| Finance | |
| Food & Drink | |
| Graphics & Design | |
| Health & Fitness | |
| Lifestyle | |
| Medical | |
| Music | |
| Navigation | |
| News | |
| Photo & Video | |
| Productivity | |
| Reference | |
| Shopping | |
| Social Networking | |
| Sports | |
| Travel | |
| Utilities | |
| Weather | |
Games:
| Category | Path |
|---|---|
| Action | |
| Adventure | |
| Board | |
| Card | |
| Casino | |
| Puzzle | |
| Racing | |
| Role-Playing | |
| Simulation | |
| Sports | |
| Strategy | |
| Trivia | |
| Word | |
访问：
https://apps.apple.com/us/charts/iphone/{category-slug}/{category-id}International Charts
应用类
Check other countries for apps not yet available or localized for the US:
- UK:
apps.apple.com/gb/charts/iphone/... - Germany:
apps.apple.com/de/charts/iphone/... - Japan:
apps.apple.com/jp/charts/iphone/... - Australia:
apps.apple.com/au/charts/iphone/... - Canada:
apps.apple.com/ca/charts/iphone/... - South Korea:
apps.apple.com/kr/charts/iphone/... - Brazil:
apps.apple.com/br/charts/iphone/...
| 品类 | 路径 |
|---|---|
| 图书 | |
| 商务 | |
| 教育 | |
| 娱乐 | |
| 财务 | |
| 美食与饮品 | |
| 图形与设计 | |
| 健康与健身 | |
| 生活方式 | |
| 医疗 | |
| 音乐 | |
| 导航 | |
| 新闻 | |
| 照片与视频 | |
| 生产力 | |
| 参考资料 | |
| 购物 | |
| 社交网络 | |
| 体育 | |
| 旅行 | |
| 实用工具 | |
| 天气 | |
What to Document
游戏类
Record the top 25-50 apps, noting:
- App name and chart position
- Rating count (proxy for install base — see references/revenue-estimation.md)
- Star rating
- Price/monetization model (free, paid, subscription, freemium)
- Brief description
- Last updated date (visible on the app's detail page)
| 品类 | 路径 |
|---|---|
| 动作 | |
| 冒险 | |
| 桌游 | |
| 卡牌 | |
| 赌场 | |
| 益智 | |
| 竞速 | |
| 角色扮演 | |
| 模拟 | |
| 体育 | |
| 策略 | |
| 问答 | |
| 文字 | |
Pattern Recognition
国际榜单
| Rating Count | Signal |
|---|---|
| >100K | Saturated — dominated by big players |
| 10K-100K | Established demand, strong competition |
| 1K-10K | Sweet spot — proven demand, beatable |
| 500-1K | Emerging niche — validate demand carefully |
| <500 | Possible new/underserved niche OR no real demand |
查看其他国家的榜单，寻找尚未在美国上线或本地化的应用：
- 英国：
apps.apple.com/gb/charts/iphone/... - 德国：
apps.apple.com/de/charts/iphone/... - 日本：
apps.apple.com/jp/charts/iphone/... - 澳大利亚：
apps.apple.com/au/charts/iphone/... - 加拿大：
apps.apple.com/ca/charts/iphone/... - 韩国：
apps.apple.com/kr/charts/iphone/... - 巴西：
apps.apple.com/br/charts/iphone/...
Step 3: Community & Demand Research
需要记录的内容
Validate that real demand exists outside the App Store. See
references/research-sources.md for detailed
search patterns and sources.
记录前25-50个应用，并标注：
- 应用名称和榜单排名
- 评分数量（安装量的替代指标——参考references/revenue-estimation.md）
- 星级评分
- 价格/变现模式（免费、付费、订阅、免费增值）
- 简要描述
- 最后更新日期（在应用详情页可见）
Reddit & Forum Research
模式识别
Search Reddit for unmet demand signals in the category. Look for:
- "Is there an app that..." posts with no good answer
- Complaints about existing apps (pain points users will pay to escape)
- Feature requests with high upvotes
- "I switched from X to Y because..." (switching triggers)
- "I'd pay $X for..." (willingness-to-pay signals)
| 评分数量 | 信号说明 |
|---|---|
| >10万 | 饱和——由大型厂商主导 |
| 1万-10万 | 需求已确立，竞争激烈 |
| 1千-1万 | 黄金区间——需求已验证，可击败现有竞品 |
| 500-1千 | 新兴细分领域——需谨慎验证需求 |
| <500 | 可能是未被充分服务的新领域 OR 无真实需求 |
Google Trends Validation
步骤3：社区与需求调研
Check Google Trends for the core problem keywords:
- Rising trend = growing demand, may not be saturated
- Declining trend = caution, avoid unless you have a unique angle
- Note seasonal patterns to time your launch (fitness peaks January, etc.)
验证App Store之外是否存在真实需求。详细的搜索模式和来源请参考references/research-sources.md。
Web → Mobile Gap Detection
Reddit与论坛调研
Search for opportunities where demand exists but no quality iOS app serves it:
- Product Hunt: Recently launched web tools in the category without native iOS apps
- AlternativeTo: What users are looking for alternatives to (dissatisfaction signal)
- International apps: Successful apps in other countries without US presence
在Reddit上搜索该品类中未被满足的需求信号。重点关注：
- “有没有一款应用可以...”且没有优质答案的帖子
- 对现有应用的投诉（用户愿意付费解决的痛点）
- 获赞量高的功能请求
- “我从X换成Y是因为...”（用户切换的触发因素）
- “我愿意付X美元购买...”（付费意愿信号）
Indie Revenue Intelligence
Google Trends验证
Search IndieHackers and Twitter (#buildinpublic) for real revenue data from solo
devs and small teams in the category. Real numbers beat estimates. See
references/research-sources.md for search
patterns.
使用Google Trends查看核心问题关键词的趋势：
- 上升趋势 = 需求增长，可能尚未饱和
- 下降趋势 = 需谨慎，除非你有独特切入点
- 注意季节性模式，以便规划发布时间（例如健身应用在1月达到峰值）
Step 4: Competitor Deep-Dive
网页→移动端缺口检测
For each promising niche area, deep-dive into 5-8 competitor apps.
寻找存在需求但没有优质iOS应用满足的机会：
- Product Hunt：该品类中近期上线但无原生iOS应用的网页工具
- AlternativeTo：用户正在寻找替代方案的应用（不满信号）
- 国际应用：在其他国家成功但未进入美国市场的应用
Data to Collect Per App
独立开发者收益情报
| Field | How to Find |
|---|---|
| Name | App Store listing |
| Ratings count | App Store listing |
| Star rating | App Store listing |
| Price / subscription | App Store listing |
| Last updated | App Store listing — stale (6+ months) = vulnerable |
| App size | App Store listing — bloated (200MB+) = simplifier play |
| Developer | App Store listing — solo dev vs company? |
| Dev replies to reviews | App Store reviews — silence = likely abandoned |
| Trustpilot score | Search |
| Estimated revenue | See references/revenue-estimation.md |
| Key features | Store description / screenshots |
| Top complaints | 1-2 star reviews on App Store and Trustpilot |
| Missing features | Compare across competitors |
| Privacy labels | App Store "App Privacy" section — data hungry = privacy play opportunity |
在IndieHackers和Twitter（#buildinpublic）上搜索该品类中独立开发者和小团队的真实收益数据。真实数据优于预估。搜索模式请参考references/research-sources.md。
Systematic Review Mining
步骤4：竞品深度分析
For each competitor, read the 20 most recent 1-star and 2-star reviews on the
App Store. Categorize complaints into:
- Bugs/crashes — Technical issues (less useful for opportunity finding)
- Missing features — "I wish it had..." (direct feature gap signals)
- UX frustration — "Too complicated", "Can't find..." (design opportunity)
- Pricing complaints — "Too expensive for what it does" (pricing opportunity)
- Broken promises — "Doesn't do what it says" (trust/quality opportunity)
- Privacy/data concerns — "Why does it need my email?" (privacy play opportunity)
- Subscription fatigue — "Not worth the monthly cost" (lifetime pricing opportunity)
The most valuable complaints are missing features and UX frustration —
these are problems you can solve. If the same complaint appears across 3+
competitors, you've found a validated gap.
针对每个有潜力的细分领域，深度分析5-8个竞品应用。
Opportunity Archetypes
每个应用需收集的数据
When analyzing competitors, identify which archetype fits the opportunity. This
sharpens positioning and guides the PRD:
| Archetype | Signal | Your Play |
|---|---|---|
| The Simplifier | Market leader is bloated, 200MB+, does too much | Focused app that does 1 thing perfectly |
| The Privacy Play | Competitors harvest data, require accounts | Privacy-first, local-only, no account needed |
| The Design Upgrade | Competitors are functional but visually dated | Same core features, premium modern UI |
| The Unbundler | Big app has 10 features, users only need 2 | Extract the 2 features into a clean app |
| The Combiner | Users always pair 2 separate apps together | Merge them into one seamless experience |
| The Localizer | App thrives in other countries, no US equivalent | Bring the validated concept to a new market |
| The AI Upgrader | Existing apps are manual/static | Add AI to automate or personalize the experience |
| The Lifetime Play | Users hate subscriptions in this category | Offer lifetime purchase where competitors don't |
Most successful indie apps fit one or more of these archetypes. Name the
archetype in the opportunity report — it clarifies the "why you win" story.
| 字段 | 获取方式 |
|---|---|
| 名称 | App Store列表 |
| 评分数量 | App Store列表 |
| 星级评分 | App Store列表 |
| 价格/订阅模式 | App Store列表 |
| 最后更新时间 | App Store列表——超过6个月未更新=易被替代 |
| 应用大小 | App Store列表——超过200MB=可做极简型应用机会 |
| 开发者 | App Store列表——独立开发者 vs 公司？ |
| 开发者回复评论情况 | App Store评论——无回复=可能已被放弃 |
| Trustpilot评分 | 搜索 |
| 预估收益 | 参考references/revenue-estimation.md |
| 核心功能 | 商店描述/截图 |
| 主要投诉点 | App Store和Trustpilot上的1-2星评论 |
| 缺失功能 | 对比多个竞品 |
| 隐私标签 | App Store的“应用隐私”板块——过度收集数据=隐私型应用机会 |
Red Flags (Avoid These Niches)
系统化评论挖掘
- Top app has 1M+ ratings (dominated by a giant)
- Heavy regulation with approval requirements (medical devices, financial trading, kids' apps under COPPA)
- All competitors are free with no monetization path
- Category requires ongoing content creation to retain users (news, social)
- Apple has a built-in solution (Calculator, Weather, Notes) — hard to compete with free+preinstalled
- App Store review rejection risk is high for the category (see references/app-store-review-risks.md)
针对每个竞品，阅读App Store上最近20条1星和2星评论。将投诉分类为：
- Bug/崩溃——技术问题（对寻找机会帮助较小）
- 缺失功能——“我希望它能...”（直接的功能缺口信号）
- UX困扰——“太复杂了”、“找不到...”（设计机会）
- 价格投诉——“不值这个价”（定价机会）
- 未兑现承诺——“没有做到宣传的功能”（信任/质量机会）
- 隐私/数据担忧——“为什么需要我的邮箱？”（隐私型应用机会）
- 订阅疲劳——“每月付费不值”（终身定价机会）
最有价值的投诉是缺失功能和UX困扰——这些是你可以解决的问题。如果同一投诉出现在3个以上竞品中，你就找到了已验证的缺口。
Green Flags (Pursue These Niches)
机会类型
- Top competitors have poor reviews (< 3.5 Trustpilot)
- Solo devs making $50K+/yr (proves indie viability)
- Editors' Choice app exists with low ratings (Apple promotes the niche)
- Users complain about the same missing feature across multiple apps
- Clear $5-15/mo or $15-50/yr willingness to pay
- Competitors haven't updated in 6+ months (stale, vulnerable)
- Apple is actively promoting the category (WWDC sessions, new APIs, featuring)
分析竞品时，确定机会所属的类型。这有助于明确定位并指导PRD撰写：
| 类型 | 信号 | 你的策略 |
|---|---|---|
| 极简型 | 市场领导者功能臃肿，超过200MB，功能过多 | 专注于把一件事做到极致的轻量应用 |
| 隐私型 | 竞品收集数据、要求注册账号 | 以隐私为先、本地存储、无需注册的应用 |
| 设计升级型 | 竞品功能完善但视觉风格过时 | 核心功能不变，采用现代高端UI |
| 拆分型 | 大型应用有10个功能，但用户只需要2个 | 将这2个功能提取出来做成简洁的应用 |
| 整合型 | 用户总是同时使用2个独立应用 | 将它们合并成一个无缝的体验 |
| 本地化型 | 应用在其他国家成功，但无美国版本 | 将已验证的概念引入新市场 |
| AI升级型 | 现有应用为手动/静态 | 添加AI实现自动化或个性化体验 |
| 终身定价型 | 用户反感该品类的订阅模式 | 提供竞品没有的终身购买选项 |
大多数成功的独立应用都符合一种或多种上述类型。在机会报告中注明类型——这能清晰说明“你为何能胜出”。
Step 5: Revenue Deep-Dive
红色预警（避开这些细分领域）
Revenue estimation is critical for deciding whether an opportunity is worth pursuing.
Don't rely on a single method — triangulate from multiple sources.
See references/revenue-estimation.md for the
full estimation toolkit including:
- Rating-count proxy methods (with confidence levels)
- Public revenue data sources (IndieHackers, #buildinpublic, Sensor Tower blogs)
- App Store position-to-revenue mapping
- Conversion rate and pricing benchmarks
- Revenue modeling templates for subscription, freemium, and paid apps
- 头部应用评分超过100万（被巨头主导）
- 有严格的监管审批要求（医疗设备、金融交易、符合COPPA的儿童应用）
- 所有竞品均为免费且无变现路径
- 品类需要持续创作内容以留住用户（新闻、社交）
- Apple已有内置解决方案（计算器、天气、备忘录）——难以与免费预装应用竞争
- 该品类App Store审核拒绝风险高（参考references/app-store-review-risks.md）
Quick Revenue Sanity Check
绿色信号（优先考虑这些细分领域）
For each opportunity, answer:
- What will you charge? (See pricing benchmarks in references/benchmarks.md)
- How many paying users do you need for your target revenue? (e.g., $10K/mo at $4.99/mo = 2,004 subscribers)
- Is that realistic given the total addressable market? (Compare to competitor rating counts)
- What's the revenue ceiling? (Best-case scenario if you capture 10% of the niche)
- 头部竞品评分较低（Trustpilot评分<3.5）
- 独立开发者年收入超过5万美元（证明独立开发可行）
- 存在编辑推荐但评分较低的应用（Apple正在推广该品类）
- 用户在多个竞品中抱怨相同的缺失功能
- 明确的每月5-15美元或每年15-50美元的付费意愿
- 竞品超过6个月未更新（过时，易被替代）
- Apple正在积极推广该品类（WWDC会议、新API、推荐展示）
Step 6: Gap Analysis
步骤5：收益深度分析
Create a feature comparison matrix across the top competitors:
markdown
| Feature | App A | App B | App C | App D | YOUR APP |
| --------------- | ------ | ----- | ----- | ----- | -------- |
| Core Feature 1 | Yes | Yes | No | Yes | YES |
| Core Feature 2 | No | Yes | Yes | No | YES |
| Missing Feature | No | No | No | No | YES |
| Privacy-first | No | No | No | Yes | YES |
| Offline support | No | No | Yes | No | YES |
| Price | $14.99 | $9.99 | Free | $6.99 | $4.99/yr |
| UX Quality | Poor | Good | OK | Good | Premium |
| Last Updated | 2024 | 2025 | 2023 | 2025 | NEW |The winning opportunity is where:
- Multiple competitors exist (proven demand)
- They all miss the same 1-2 features
- Users vocally complain about the gap
- Pricing is high enough to support indie revenue
- You can build a defensible advantage (see moat analysis below)
收益预估对于判断机会是否值得投入至关重要。不要依赖单一方法——结合多种来源进行交叉验证。
完整的预估工具包请参考references/revenue-estimation.md，包括：
- 基于评分数量的替代预估方法（含置信度）
- 公开收益数据源（IndieHackers、#buildinpublic、Sensor Tower博客）
- App Store排名与收益映射
- 转化率和定价基准
- 订阅、免费增值和付费应用的收益建模模板
Moat Analysis
快速收益合理性检查
For each opportunity, evaluate defensibility. Apps with no moat get cloned
quickly. Score each factor:
| Moat Type | Question | Example |
|---|---|---|
| Data moat | Does the app get better with more user data? | Personalized recommendations, learned habits |
| Network effects | Does value increase with more users? | Social features, shared content |
| Switching costs | Is it painful to leave once you've invested? | Historical data, customization, integrations |
| Brand/trust | Does the category reward reputation? | Privacy, health, finance |
| Speed moat | Can you ship and iterate faster than incumbents? | Solo dev agility vs corporate bureaucracy |
| AI moat | Does your AI improve with usage in ways competitors can't? | Custom models, unique training data |
Even one strong moat factor is valuable. "Speed moat" is the most accessible for
indie devs — ship fast, iterate based on real feedback, stay ahead.
针对每个机会，回答以下问题：
- 你将如何定价？（参考references/benchmarks.md中的定价基准）
- 达到目标收益需要多少付费用户？（例如，每月10000美元，每月订阅费4.99美元=2004名订阅用户）
- 结合总可触达市场来看，这是否现实？（与竞品评分数量对比）
- 收益上限是多少？（如果你占据该细分领域10%份额的最佳情况）
Step 7: Score & Rank Opportunities
步骤6：缺口分析
Score each candidate opportunity using the structured rubric in
references/scoring-framework.md. Score on 6
dimensions (1-5 each, 30 max): Market Demand, Competition Weakness, Revenue
Potential, Build Feasibility, Differentiation Clarity, and Regulatory Safety.
Present the scorecard to the user alongside the top 3 report.
创建功能对比矩阵，对比头部竞品：
markdown
| 功能 | 应用A | 应用B | 应用C | 应用D | 你的应用 |
| --------------- | ------ | ----- | ----- | ----- | -------- |
| 核心功能1 | 是 | 是 | 否 | 是 | 是 |
| 核心功能2 | 否 | 是 | 是 | 否 | 是 |
| 缺失功能 | 否 | 否 | 否 | 否 | 是 |
| 隐私优先 | 否 | 否 | 否 | 是 | 是 |
| 离线支持 | 否 | 否 | 是 | 否 | 是 |
| 价格 | $14.99 | $9.99 | 免费 | $6.99 | 每年$4.99 |
| UX质量 | 差 | 好 | 一般 | 好 | 高端 |
| 最后更新 | 2024 | 2025 | 2023 | 2025 | 全新 |成功的机会需满足：
- 存在多个竞品（需求已验证）
- 所有竞品都缺失相同的1-2个功能
- 用户明确抱怨该缺口
- 定价足够高以支持独立开发者收益
- 你能构建可防御的优势（见下方护城河分析）
Step 8: Top 3 Opportunity Report
护城河分析
Produce a ranked report with this structure:
markdown
undefined针对每个机会，评估其防御性。没有护城河的应用会很快被克隆。对每个因素评分：
| 护城河类型 | 问题 | 示例 |
|---|---|---|
| 数据护城河 | 应用是否会随着用户数据增多而变得更好？ | 个性化推荐、学习用户习惯 |
| 网络效应 | 用户越多，应用价值是否越高？ | 社交功能、共享内容 |
| 转换成本 | 用户投入后是否难以切换？ | 历史数据、自定义设置、集成功能 |
| 品牌/信任 | 品类是否重视声誉？ | 隐私、健康、财务 |
| 速度护城河 | 你能否比现有厂商更快地发布和迭代？ | 独立开发者的敏捷性 vs 企业官僚体系 |
| AI护城河 | 你的AI是否能通过使用实现竞品无法复制的改进？ | 自定义模型、独特训练数据 |
即使只有一个强护城河因素也很有价值。“速度护城河”对独立开发者来说最容易实现——快速发布、根据真实反馈迭代、保持领先。
Top 3 iOS App Opportunities in {Category}
步骤7：评分与排名机会
Opportunity Scorecard
—
| Dimension | Opp 1: {Name} | Opp 2: {Name} | Opp 3: {Name} |
|---|---|---|---|
| Market Demand (1-5) | |||
| Competition Weakness | |||
| Revenue Potential | |||
| Build Feasibility | |||
| Differentiation | |||
| Regulatory Safety | |||
| TOTAL (out of 30) |
使用references/scoring-framework.md中的结构化评分标准，对每个候选机会进行评分。从6个维度评分（每个维度1-5分，满分30分）：市场需求、竞品弱点、收益潜力、开发可行性、差异化清晰度、合规安全性。
将评分卡与前三机会报告一起呈现给用户。
Opportunity 1: {App Name} (RECOMMENDED)
步骤8：前三机会报告
Archetype: {Simplifier / Privacy Play / Design Upgrade / Unbundler /
Combiner / Localizer / AI Upgrader / Lifetime Play}
One-line pitch: {What it does in 10 words}
The gap: {What's missing in the market}
Target user: {Who and why they'd pay}
Revenue model: {Price point and conversion assumptions}
Revenue path: {How to reach $X/mo with math}
Competition: {Who exists, why you win}
Moat: {What defensibility you build over time}
Build complexity: {Low/Medium/High, estimated weeks to MVP}
App Store risk: {Any review/approval concerns}
Confidence: {High/Medium/Low with reasoning}
生成排名报告，结构如下：
markdown
undefinedOpportunity 2: {App Name}
{品类}下的Top 3 iOS应用机会
—
机会评分卡
{Same fields as above}
| 维度 | 机会1：{名称} | 机会2：{名称} | 机会3：{名称} |
|---|---|---|---|
| 市场需求（1-5） | |||
| 竞品弱点 | |||
| 收益潜力 | |||
| 开发可行性 | |||
| 差异化 | |||
| 合规安全性 | |||
| 总分（满分30） |
Opportunity 3: {App Name}
机会1：{应用名称}（推荐）
{Same fields as above}
类型： {极简型 / 隐私型 / 设计升级型 / 拆分型 /
整合型 / 本地化型 / AI升级型 / 终身定价型}
一句话介绍： {10字以内说明功能}
缺口： {市场中缺失的内容}
目标用户： {谁会付费，为什么}
变现模式： {定价点和转化假设}
收益路径： {通过数据说明如何达到每月X美元}
竞品： {现有竞品，你胜出的原因}
护城河： {长期构建的防御优势}
开发复杂度： {低/中/高，MVP预估开发周数}
App Store风险： {任何审核/批准相关问题}
置信度： {高/中/低及理由}
Recommendation
机会2：{应用名称}
{Why #1 is the best bet, with specific reasoning tied to scores}
**Present this to the user and get their pick before proceeding.**
---{与上述相同字段}
Step 9: Quick Validation (Optional)
机会3：{应用名称}
Before investing in a full PRD, suggest a lightweight smoke test to de-risk the
chosen opportunity:
- Reddit validation post: Post in a relevant subreddit describing the concept and ask if people would use/pay for it. Frame as "I'm thinking about building X — would this solve your problem?"
- Landing page test: Create a simple one-page site describing the app with an email signup. Use Carrd, Framer, or a single HTML page. Run for 3-7 days.
- Twitter/X poll: Post a poll describing the problem and 3-4 solution approaches. See which resonates.
- TestFlight beta list: Start collecting emails for early beta access — this validates willingness to actually try the app.
Skip this step if: the user wants to move fast, the opportunity scored 24+, or
strong demand evidence already exists from Step 3.
{与上述相同字段}
Step 10: Write the MVP PRD
推荐理由
Once the user selects an opportunity, write a comprehensive PRD with these
sections:
- Executive Summary — One paragraph pitch, name the opportunity archetype
- Market Opportunity — Problem, TAM/SAM/SOM market sizing (see below), competitive landscape table, revenue validation
- Target Users — 3 personas with name, age, job, pain points, willingness to pay
- MVP Feature Set — 5-8 feature groups with detailed specs, UI behavior, edge cases. Clearly mark what's MVP vs V2.
- Screen Map — All screens listed with parent/child relationships
- Onboarding Flow — First-time user experience step by step: what the user sees on first launch, how many screens before value delivery, what permissions are requested and when, how the app demonstrates its core value within 60 seconds. This is the single biggest factor in retention.
- User Flow — Primary user journey from onboarding to daily use
- Monetization — Free vs Premium feature split, pricing (annual + lifetime), free trial length, Superwall/RevenueCat integration, paywall placement strategy
- Tech Stack — Swift/SwiftUI, minimum iOS version, persistence (SwiftData/ CoreData/UserDefaults), networking, third-party dependencies. Keep dependencies minimal for long-term maintainability.
- AI Features — If applicable, what AI does and doesn't do, on-device vs cloud, cost implications
- Data Models — Swift structs/classes for core entities with property types
- Design Direction — Color palette (with hex codes), typography, component style, mood. Reference Apple's Human Interface Guidelines.
- App Store Listing (ASO) — Optimized for discoverability:
- App name (30 char max) — include primary keyword
- Subtitle (30 char max) — reinforce value proposition with secondary keyword
- Keywords (100 char max, comma-separated) — no spaces after commas, no duplicates of words in name/subtitle, include misspellings and synonyms
- First 3 lines of description — these show before "Read More" tap, must hook immediately
- Screenshot strategy — what each of the 10 screenshots should show, captions for each
- App preview video — 15-30 second concept showing core value proposition
- See references/aso-guide.md for keyword research methodology and optimization tactics
- Launch Strategy — Week 1-12 plan, marketing channels, content strategy
- Success Metrics & Retention — KPIs with specific targets including D1/D7/D30 retention benchmarks
- Risks & Mitigations — Top 5 risks with solutions, including App Store review risks
- Privacy & Compliance — Privacy nutrition labels, App Tracking Transparency, data handling, App Store Review Guidelines compliance
- Competitive Moat — How defensibility builds over time
- Future Roadmap — V2, V3 features beyond MVP
{为什么机会1是最佳选择，结合评分给出具体理由}
**将报告呈现给用户，待用户选择后再继续下一步。**
---Market Sizing Framework
步骤9：快速验证（可选）
For section 2, estimate:
- TAM (Total Addressable Market): Total number of people with this problem × willingness to pay. Use Google Trends, Statista, and category research.
- SAM (Serviceable Addressable Market): TAM filtered to iOS users in your target geography.
- SOM (Serviceable Obtainable Market): Realistic capture in year 1. For indie apps, 0.1-1% of SAM is a reasonable starting estimate. Compare to competitor rating counts for grounding.
Save the PRD as:
PRD-{AppName}.md在投入撰写完整PRD之前，建议进行轻量级的冒烟测试以降低所选机会的风险：
- Reddit验证帖：在相关子版块发布帖子描述应用概念，询问用户是否会使用/付费。例如：“我正在考虑开发X——这能解决你的问题吗？”
- 着陆页测试：创建一个简单的单页网站描述应用，提供邮箱注册入口。使用Carrd、Framer或单页HTML。运行3-7天。
- Twitter/X投票：发布投票描述问题和3-4种解决方案，查看哪种最受欢迎。
- TestFlight测试名单：开始收集早期测试用户的邮箱——这能验证用户是否愿意尝试应用。
如果出现以下情况可跳过此步骤：用户希望快速推进、机会评分24分以上、步骤3已找到强烈的需求证据。
Revenue & Marketing Benchmarks
步骤10：撰写MVP PRD
See references/benchmarks.md for revenue validation
benchmarks, pricing sweet spots, retention targets, and marketing channel
playbook. Reference this when validating opportunities in Steps 5-7 and writing
the launch strategy in Step 10.
用户选定机会后，撰写全面的PRD，包含以下部分：
- 执行摘要——一段介绍，注明机会类型
- 市场机会——问题、TAM/SAM/SOM市场规模（见下文）、竞争格局表、收益验证
- 目标用户——3个用户画像，包含姓名、年龄、职业、痛点、付费意愿
- MVP功能集——5-8个功能组，含详细规格、UI行为、边缘情况。明确标注哪些是MVP功能，哪些是V2功能。
- 页面地图——列出所有页面及父子关系
- 引导流程——首次用户体验步骤：首次启动时用户看到的内容、获得价值前的页面数、请求权限的时机和方式、如何在60秒内展示核心价值。这是影响留存率的最大因素。
- 用户流程——从引导到日常使用的主要用户旅程
- 变现策略——免费 vs 付费功能划分、定价（年度+终身）、免费试用时长、Superwall/RevenueCat集成、付费墙放置策略
- 技术栈——Swift/SwiftUI、最低iOS版本、持久化方案（SwiftData/ CoreData/UserDefaults）、网络、第三方依赖。尽量减少依赖以保证长期可维护性。
- AI功能——如有，说明AI的作用和局限性、本地部署 vs 云端部署、成本影响
- 数据模型——核心实体的Swift结构体/类及属性类型
- 设计方向——调色板（含十六进制代码）、排版、组件风格、氛围。参考Apple的人机界面指南。
- App Store列表（ASO）——优化以提升可发现性：
- 应用名称（最多30字符）——包含主关键词
- 副标题（最多30字符）——用次要关键词强化价值主张
- 关键词（最多100字符，逗号分隔）——逗号后无空格，不重复名称/副标题中的单词，包含拼写错误和同义词
- 描述前3行——点击“查看更多”前会显示，必须立即吸引用户
- 截图策略——说明10张截图各自展示的内容，每张截图配说明
- 应用预览视频——15-30秒的概念视频，展示核心价值主张
- 关键词研究方法和优化技巧请参考references/aso-guide.md
- 发布策略——第1-12周计划、营销渠道、内容策略
- 成功指标与留存——带具体目标的KPI，包括D1/D7/D30留存基准
- 风险与缓解措施——Top 5风险及解决方案，包括App Store审核风险
- 隐私与合规——隐私营养标签、App Tracking Transparency、数据处理、App Store审核指南合规
- 竞争护城河——如何长期构建防御优势
- 未来 roadmap——MVP之外的V2、V3功能
—
市场规模框架
—
在第2部分中，预估：
- TAM（总可触达市场）：有该问题的总人数 × 付费意愿。使用Google Trends、Statista和品类调研数据。
- SAM（可服务触达市场）：TAM过滤为目标地区的iOS用户。
- SOM（可获得服务市场）：第一年的实际获取量。对于独立应用，0.1-1%的SAM是合理的初始预估。可与竞品评分数量对比以验证。
PRD保存为：
PRD-{AppName}.md—
收益与营销基准
—
收益验证基准、定价黄金区间、留存目标和营销渠道手册请参考references/benchmarks.md。在步骤5-7验证机会和步骤10撰写发布策略时可参考此文档。