TL;DR
The apps already on the stores are a map of proven demand. Read their reviews for what people wish they had, look for bloated apps you could simplify, and find the narrow user a big app ignores. Existing apps prove people already pay for the problem.
Existing apps are one of the best idea sources you have, because they prove people already want the problem solved. The trick is not to clone them, but to read what their users complain about and wish for. The builders who find winning angles here treat the App Store and Google Play as research, mining reviews and gaps rather than copying whole apps.
Read the reviews for what is missing
Reviews are a free list of unmet needs, so a little reading does the heavy lifting. Open the popular apps in a category and read the three- and four-star reviews closely. Those are people who like the app but wish it did something more, and each wish is a possible app idea.
- Feature requests: the thing reviewers keep asking the app to add.
- Bloat complaints: an app so packed people want a simpler version.
- Ignored users: a niche the big app treats as an afterthought.
- Pricing gripes: an expensive app a cheaper focused tool could beat.
Look for the simpler version
Many popular apps grow bloated over time, and that is your opening. If a top app is stuffed with features most people never touch, a clean app that does just the core job can win the users who feel overwhelmed. Simpler and clearer is a real angle, especially for a beginner who cannot out-feature a big team anyway.
Find the narrow user they ignore
Big general apps cannot serve everyone perfectly, so they leave specific users underserved. A generic habit tracker is not built for one particular routine; a broad planner is not tuned to one profession. Pick the narrow user a popular app treats as an afterthought and build the app that fits them exactly.
Keep it research, not copying
The goal is inspiration, not imitation. Copying a whole app gets you a crowded, low-value clone that Apple's rules discourage anyway. Use existing apps to confirm demand and reveal gaps, then build your own narrow answer. Read widely, note the openings, and build the app the reviews are quietly asking for.
Common questions
How do reviews help me find app ideas?
Three- and four-star reviews are full of people who like an app but wish it did more. Each wish is a possible feature or a whole new app aimed at that gap. Read them closely to find demand that already exists.
Is it okay to build an app similar to a popular one?
Building a narrow, improved version aimed at a specific user is fine and common. Cloning a whole app is not, since it creates a low-value copy Apple discourages. Use existing apps for research, then build your own focused angle.
How do I find a gap a big app leaves open?
Look for feature requests, bloat complaints, ignored niches, and pricing gripes in the reviews. Those weaknesses are exactly what a focused app can beat. The gap between a bloated app and a clean one is your opening.
Why build a simpler app than a popular one?
Many top apps grow overloaded, and a clean app doing just the core job wins the users who feel overwhelmed. Simpler is a real angle a beginner can execute. You cannot out-feature a big team, but you can out-focus them.
How many apps should I study in a category?
Read the top handful closely, since they set the norms and reveal the gaps. A dozen reviews across a few apps shows both what people want and what is missing. More than that yields little extra signal.
What if every idea I have already exists?
That usually confirms demand, which is good. Pick a narrow angle or a specific user the existing apps ignore rather than a generic clone. A focused version of a proven idea is a strong beginner move.
Keep going
Mine existing apps for the gaps their users keep asking about.
Get the other 37 in the app user stack, plus the full App Store Launch Club community - $9/mo, cancel anytime.
Join the Club