App Store Opportunity Research

Prerequisites

• 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

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 PRD

Step 1: Define the Category & Goals

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:

1. What category or problem space interests you?
2. Consumer or B2B? (Consumer is easier to validate quickly)
3. Any budget constraints? (No-AI = cheaper to build, AI = higher ceiling)
4. Target revenue? ($1K/mo side project vs $10K/mo business vs $50K+/mo full-time replacement)
5. What's your timeline? (2-4 week MVP vs 2-3 month polished launch)
6. Do you have domain expertise or personal pain in this area? (Strongest apps come from scratching your own itch)

Step 2: App Store Charts Research

Browse the iOS App Store charts to map the competitive landscape.

Chart URLs

Navigate to: https://apps.apple.com/us/charts/iphone/{category-slug}/{category-id}

Apps:

Games:

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

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.

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)

Google Trends Validation

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

Web → Mobile Gap Detection

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

Indie Revenue Intelligence

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.

Step 4: Competitor Deep-Dive

For each promising niche area, deep-dive into 5-8 competitor apps.

Data to Collect Per App

Systematic Review Mining

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.

Opportunity Archetypes

When analyzing competitors, identify which archetype fits the opportunity. This sharpens positioning and guides the PRD:

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.

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)

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)

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

Quick Revenue Sanity Check

For each opportunity, answer:

1. What will you charge? (See pricing benchmarks in references/benchmarks.md)
2. How many paying users do you need for your target revenue? (e.g., $10K/mo at $4.99/mo = 2,004 subscribers)
3. Is that realistic given the total addressable market? (Compare to competitor rating counts)
4. What's the revenue ceiling? (Best-case scenario if you capture 10% of the niche)

Step 6: Gap Analysis

Create a feature comparison matrix across the top competitors:

| 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:

1. Multiple competitors exist (proven demand)
2. They all miss the same 1-2 features
3. Users vocally complain about the gap
4. Pricing is high enough to support indie revenue
5. You can build a defensible advantage (see moat analysis below)