$ cat prompt.txt — App Development
Mobile App Idea Validator — Ship-Worthy or Pivot in 30 Min
Score an app idea against App Store reality: demand, monetisation, build cost, and ASO viability.
Indie app graveyards are full of beautifully-built apps in dead niches. This prompt stress-tests your app idea against the 5 levers that actually determine whether it makes money: organic search demand (ASO), monetisation model fit, build complexity, retention prospects, and the App Store competitive moat. Output is a green/yellow/red verdict with a specific pivot if the idea is salvageable.
$ cat prompt.txt | pbcopy
The prompt — copy & paste
You are an indie app developer who has shipped 12 apps to the App Store, with 3 hitting $5k+ MRR. Your job is to validate the app idea below using a 5-lever framework. Be honest — most indie app ideas fail one of these levers and shouldn't be built.
MY APP IDEA: {{app_idea}}
PLATFORM PREFERENCE: {{platform_preference}} (iOS / Android / Both)
MONETISATION PREFERENCE: {{monetisation_preference}} (Subscription / IAP / Paid upfront / Ads / Freemium)
MY BUILD SKILL: {{build_skill}} (e.g. "Solo iOS dev, SwiftUI, 5 years experience" or "Junior, learning Flutter, 6 months experience")
EXECUTE THE 5-LEVER ANALYSIS:
LEVER 1 — ASO DEMAND (App Store Optimisation viability)
This is the #1 lever for indie apps because organic search is the only free distribution channel.
- What 3-5 App Store search queries would my target user type to find this app?
- For each query, estimate: search volume (high/mid/low), Top 10 competition strength (1-5), brand-keyword domination (do household-name apps already own the slot?)
- VERDICT: Can a polished launch reasonably rank Top 10 for at least 2 of these queries within 90 days? GREEN / YELLOW / RED.
LEVER 2 — MONETISATION FIT
Match the {{monetisation_preference}} to the app type:
- SUBSCRIPTION → only works for apps users open 4+ times/week (habit tools, productivity, fitness, journalling). Apps used once a month die on subscription.
- IAP (one-time unlocks) → works for utility/gaming apps with clear "free vs paid" feature gates.
- PAID UPFRONT → tough sell in 2026 unless you have built-in audience or strong category trust.
- ADS → only viable at 50k+ DAU. Don't pick this for an indie launch.
- FREEMIUM → table-stakes default for most consumer apps.
VERDICT: Does the chosen model fit my app's actual use pattern? GREEN / YELLOW / RED + recommended monetisation if I picked wrong.
LEVER 3 — BUILD COMPLEXITY vs MY SKILL
For my {{build_skill}}, estimate:
- Realistic time to MVP (skill-adjusted): X weeks
- Stack the AI is most likely to write correctly for this app type (Swift/SwiftUI native, Flutter, React Native, Expo)
- Required backend complexity (none / Firebase / Supabase / custom — the higher the backend complexity, the more likely a solo founder gets stuck)
- 3 specific technical risks (e.g. "Background HealthKit sync is fragile", "Push notification CSAT depends on backend reliability")
VERDICT: Can I realistically ship a polished MVP in <12 weeks at my skill level? GREEN / YELLOW / RED.
LEVER 4 — RETENTION PROSPECTS
Indie apps live or die by 30-day retention. For this app type, estimate:
- Default category D30 retention (research benchmark + reasoning)
- 2-3 specific retention mechanics this app type needs to even achieve category-average retention (notifications, streaks, social, content freshness, etc.)
- Will my MVP scope realistically include those mechanics? Or am I shipping a high-churn app?
VERDICT: GREEN / YELLOW / RED + the ONE retention mechanic that's most critical to ship in v1.
LEVER 5 — COMPETITIVE MOAT
Why won't the existing top-3 apps in this category crush me?
- List the top 3 incumbents (by name if you know them, by description otherwise)
- For each, identify ONE specific weakness in their app that I could exploit (UI dated, feature gap, pricing pain, niche they ignore)
- State the one-sentence wedge: "My app is the only [category] app that [specific differentiation]"
- "I'll be better/cheaper" IS NOT A WEDGE.
VERDICT: Do I have a wedge that justifies the user switching cost? GREEN / YELLOW / RED.
FINAL VERDICT
- ALL 5 GREEN → Ship it. State the 30-day MVP scope (V1 features only — be ruthless on cuts).
- 1-2 YELLOWS → Pivot. State the specific pivot (could be: change platform, change monetisation, narrow the niche, change the wedge).
- 3+ YELLOWS or any RED → Kill it OR fundamental rethink. Suggest 3 alternative app ideas that use my same {{build_skill}} + {{platform_preference}} but pass more levers.
Be brutally honest. Saving me 12 weeks on the wrong app is worth more than approving a bad idea to be nice.$ variables_to_fill_in
$ man playbook
Step-by-step playbook
How to actually use this prompt for the best results.
- 01
Describe the app in one sentence + one main feature
{{app_idea}} should be one sentence: 'an iOS app that helps freelance designers track which Figma files they've sent to which clients'. Skip the feature lists — the prompt will scope the MVP itself.
- 02
Be honest about your skill level
Indie app developers chronically overestimate their delivery speed. If you're learning SwiftUI, say so. The build-complexity lever calibrates against your reality, not against an idealised version of you.
- 03
Don't argue with red flags
If any lever returns RED, the natural reaction is to defend. Resist. The prompt is calibrated against actual indie failure modes. Either accept the pivot or pick a different idea.
- 04
If GREEN — scope the MVP ruthlessly
The model will recommend a 30-day MVP scope. Cut it by 30% more. Indie MVPs always ship late and overscoped; pre-cutting prevents the worst version of this.
- 05
Use the ASO prompt next
Once you've decided to build, use the 'App Store Listing Optimizer' prompt to set up your App Store Connect listing for the keywords identified in Lever 1. Listing setup is more valuable than 90% of feature work.
$ man tips
Pro tips for better output
- ›Run the prompt twice with different platform_preference values — many ideas only work on iOS (subscription monetisation, high paying users) but fail on Android. Pick the platform first based on validation results.
- ›If the wedge in Lever 5 is weak, the app will struggle to grow even with a perfect launch. Wedge > features > polish > marketing in order of impact.
- ›Indie apps that succeed almost always solve a problem the founder personally has. If you're building this for 'other people' you don't know intimately, the model will probably (correctly) score Lever 5 as RED.
- ›Save the ASO keywords from Lever 1 — these become your App Store Connect setup the day you start dev, not the day you ship.
$ echo $YIELD
What you'll get
A 5-lever scored analysis of your app idea with GREEN/YELLOW/RED verdicts per lever and a final SHIP/PIVOT/KILL recommendation — with a 30-day MVP scope (if greenlit) or a specific pivot (if not).
$ man faq
FAQ
Should I build iOS or Android first as an indie?
iOS first if you're targeting paid apps or subscriptions — US/UK/EU iOS users pay 3-5x more per user than Android. Android first if you're targeting markets like India, SEA, LATAM, or running ad-supported apps. Almost never both at launch — split focus kills indie apps.
Can AI actually validate apps without market research?
AI validation captures 70-80% of what 5 customer interviews would surface, in 1/20th the time. It's a strong first filter. Always pair it with at least 3 real user interviews before writing code — patterns the AI misses (UI preferences, willingness to pay specifically, switching cost) show up fast in interviews.
$ ls /prompts/app-development
Related prompts
$ cd /prompts — explore all 48 free AI prompts on ClaudeSkill