How to find app ideas that make money: follow the angry reviews

You searched for app ideas that make money and got a list of 50 ideas: a habit tracker, a recipe app, a fitness app. Every one of those already has hundreds of competitors, and the list does not tell you which one will earn.

The developers who actually get paid on the App Store rarely start from a list. They start from apps people already pay for, read what those users hate, and build the fix. This page walks through that method step by step, with a scoring table, a worked example and the mistakes that cost indie developers months.

A quick definition first. A profitable app idea here means a small app one person can build in weeks that strangers find through App Store search and pay for, through a subscription or a one time unlock. Not a startup. Not a social network.

What makes an app idea make money?

An app idea makes money when three things are true at once: people already search for it, they already pay for apps like it, and the current apps leave a complaint unsolved. Originality is not on the list.

A popular reply in r/iOSProgramming put it simply: if there is an app for it, there is a market. Another commenter in the same thread pointed out that Amazon was not the first online store and Google was not the first search engine. For a solo developer, existing competitors are proof of demand, not a reason to quit.

If an idea scores on all five, it is worth building. If it fails the first two, no amount of polish will save it.

The angry reviews method, step by step

The short version: find apps with thousands of ratings and angry reviews, then build the fix. A developer who has run a mobile app studio profitably for 15 years described this exact loop in r/iOSProgramming, and it is the method behind most of the "my boring app got its first sale" posts in r/AppBusiness.

1. Pick a category you know a little about. A hobby, a job or a household chore. Knowing the users makes the reviews easier to read.
2. Search the App Store for the obvious terms in that category and open the top 5 to 10 apps.
3. Keep the apps with thousands of ratings. A handful of ratings means nobody searches for it.
4. Sort reviews by most recent and read the 1 and 2 star ones. Recent matters: old complaints may already be fixed.
5. Tally the complaints. Copy each into a sheet and count repeats across apps. Three apps with the same complaint beats one app with ten.
6. Write the fix in one sentence and check it can be built in two to four weeks, on device, by you.

What the complaints usually look like

Most one star reviews fall into a few buckets, and each one points to a different kind of app:

• "Doesn't work" (inaccurate, crashes, wrong results): build the accurate version.
• "Too many ads" or "everything is paywalled": build a clean version with an honest price.
• "Too complicated": build the one feature most people want, nothing else.
• "Missing X" (no widget, no Apple Watch, no offline mode): build the version with X.
• "Changed and ruined it": build what the old version did.

Tip: Ignore complaints about price alone. People who hate paying anything are not your customers. Complaints about quality from people who already paid are gold.

A worked example: the satellite dish app

The playbook example comes from an r/AppBusiness post titled "I built the most boring app I could think of. Someone actually paid for it." The developer picked a dull utility category, satellite dish alignment, and read the one star reviews of the leaders. The complaints were concrete: the compass was inaccurate and the screen was unreadable outdoors in sunlight.

So the fix was concrete too: an accurate pointing tool with a high contrast screen you can read on a roof. Nothing about it was original. It got a paying customer.

The comments are as useful as the post. One reply argued that search beats TikTok for an app like this: people who need to align a dish search for a tool at that exact moment, so App Store keywords matter more than viral video. Another developer said they published an egg incubation tracker and got a first paying customer within two to three days, adding that "extremely niche consumer apps are the way to go" because non technical buyers pay instead of thinking they can build it themselves.

The same thread also shows the honest range. One developer reported 6 sales in about 6 months from a 0 to 60 timing app. Another got 2 sales in 6 weeks from a minimal weekly planner with no promotion. A first sale proves the idea, not the income, and results vary a lot.

Where else to find app ideas that pay

Review mining is the core method, but these sources feed it:

• App Store search suggestions. Type the start of a phrase and note what autocompletes. A commenter in r/iOSProgramming put the advice as: find high traffic keywords without huge competition and build an app around that keyword.
• Your job or hobby. One r/androiddev reply said to make something very niche that you are a consumer of. You understand the users and can test it yourself.
• Your own annoyances, then generalize. An r/AppStoreOptimization developer started with an alarm that was softer at 1 AM, then grew it into a calendar based schedule tool once users asked for more. Your own problem gets you the first version; strangers decide the rest.
• Reddit and forums for a specific group. Hobby subreddits, Facebook groups and trade forums where people ask "is there an app that..." are lists of unsolved problems.
• Better versions of a hit. A blunt r/androiddev reply said you have better odds making a clone of a successful app with better performance, a cleaner interface or a lower price. Fix the complaints rather than copying the design.

The App Store Apps pack turns this into a repeatable worksheet: the gap finding checklist, how to read the leaders' listings, and how to pick the keyword your app is named after.

How to check an idea before you build it

Validate with what the App Store already shows you, then with a fast small build. You do not need a survey or a landing page for a small utility.

1. Demand: do at least two or three apps in the niche have thousands of ratings?
2. Payment: does at least one top app sell a subscription or unlock? If every app is free with ads, the buyers may not pay.
3. Gap: do recent low reviews repeat a complaint you can fix?
4. Scope: can you build the fix in two to four weeks with no server? An r/androiddev developer recommended ideas that work totally on device, because it makes everything more achievable.
5. Name: can the main search term go in your app name and subtitle?

Then ship a small first version. Real installs and trial starts are better validation than any opinion. For what "working" looks like in numbers, see how much indie apps make per month and how many downloads it takes to make $1,000 a month.

Watch out: Apple keeps 30% of sales, or 15% in the App Store Small Business Program for developers under $1 million a year in proceeds, according to Apple's developer site. Price with that cut in mind.

Mistakes that kill good app ideas

These are the patterns that come up again and again in the threads:

• Chasing originality. Hunting for an idea nobody has built usually means hunting for a market nobody pays in.
• Building a broad app. "A productivity app" competes with giants. "A shift calendar for nurses" competes with a few small apps.
• Picking ideas that need users to exist first. Social apps, marketplaces and anything that needs both sides is close to impossible solo.
• Ignoring distribution. Even the egg tracker developer said distribution is the real bottleneck. Choose an idea people search for by name, so the App Store does the marketing.
• Starting over too soon. One r/androiddev reply warned: if your app gains traction, invest in it rather than starting another project from zero.
• Polishing for months. Ship a small version, read your own reviews, and let users shape the next feature.

Do you need to code to build it?

No. Many of these small utilities can be built with AI coding tools or no code builders, though anything that needs sensors or precise device features goes faster with some Swift. If you have never coded, read how to make an app without coding and earn money for the realistic options and costs.

Where to go from here

Here is a plan you can start this week:

1. Pick one category you know and list the top 10 apps in it.
2. Keep the ones with thousands of ratings and read 30 recent one and two star reviews each.
3. Tally the complaints and pick the one that repeats across apps.
4. Score it against the five signals in the table above.
5. Build the smallest fix in two to four weeks, named after the search term, and ship it.

The App Store Apps pack covers what comes after the idea, in 24 lessons across 6 modules: the listing that ranks, the paywall and pricing tests, and getting installs without paid ads, with the checklists and templates indie developers used. It is $19, or all 16 Money Printer packs are $39.