Most "should I build this?" advice is too vague to be useful ("talk to customers!"). For an indie iOS developer, app idea validation has a tighter definition: can I find a keyword I can rank for, where users want something better than what currently exists, and where the market can support a real business?
The 4-question validation framework
Run a candidate idea through these. If three of four are "yes," it's worth a real prototype. If two or fewer, you're picking a fight you'll lose.
1. Is there demand?
Search the keyword you'd target on the App Store. If autocomplete completes it, demand exists. If autocomplete doesn't, you're betting that demand will appear — that's a much harder bet.
A more rigorous read: look at Peekaso's search-demand score for the keyword. ≥40 means real, recurring search volume. Below 15 means you're chasing a trickle.
2. Can you rank?
This is where most ideas die. If the top 5 apps for your target keyword are:
- All actively maintained (<6 months since last update)
- All rated 4.5+ stars
- All with 10,000+ reviews
- All from real companies
You're competing against entrenched apps. Even a meaningfully better product will take 12+ months to dent the top of search. For most indies, that's not a winnable fight.
But if any of those are missing — stale incumbents, unhappy users, weak brand presence — you have an opening. Peekaso's chance-to-rank score is a single number that captures this; aim for ≥50% for a realistic shot.
3. Are users unhappy?
Read the last 50 reviews of each of the top 3 apps. You're looking for repeated complaints. One person hating an app is noise; thirty people hating the same thing is your product spec.
Common patterns to watch for:
- "Used to be great until..." (a known regression)
- "Why doesn't it have X?" (feature gap)
- "Crashes constantly" (reliability gap)
- "Too expensive for what it does" (pricing opening)
- "Annoying ads" (monetization opening)
If you can't find a repeated complaint, the category is well-served. That's a hard market to enter.
4. Will users pay?
Look at the top apps' monetization. If they're paid downloads, paid IAPs, or subscriptions — users in this space pay. You can build with confidence that an indie-friendly $4.99/year subscription has a chance.
If everything in the top 10 is free with ads, your monetization options narrow. Ad revenue at indie scale is brutal — you'd need hundreds of thousands of installs to make rent.
Peekaso flags the monetization signal for each keyword (strong/moderate/weak/ad-supported). "Strong" or "moderate" means users in this space convert.
The 90-minute pre-build checklist
Before you write a single line of code, spend 90 minutes:
- List 3-5 candidate keywords you'd target.
- Run each through Peekaso's search and screenshot the competitive-landscape panel.
- For each, read the top 3 apps' last 30 reviews. Note repeated complaints.
- Run the 4-question framework against each. Pick the one with the most "yes" answers.
- Write a single paragraph: "I'm building X for [audience], to solve [problem that incumbent isn't solving]. My differentiation is [Y]."
If you can't write that paragraph at the end of 90 minutes, you don't yet have a validated idea. That's fine — pick a different angle and try again. The 90 minutes are cheap. The six months you'd otherwise spend building the wrong thing are not.
What validation doesn't tell you
This framework tells you whether the market is viable. It does not tell you:
- Whether you can build the product in a reasonable timeframe.
- Whether you can market it after launch (organic ranking helps, but it's not enough alone).
- Whether your specific positioning will land with users (that requires shipping and iterating).
What it does do: stop you from building in a market that will never reward the effort. That alone is worth the 90 minutes.
Start with the best-odds explore tab if you don't have a specific idea yet, or search a keyword directly in Peekaso if you do.