How to find app ideas that sell is the question that decides whether your make-money-from-home plan works, because the single most expensive mistake an indie iOS developer can make is building the wrong app. I've watched smart developers spend six months on beautifully crafted apps nobody downloads, while less talented developers ship mediocre apps in their niche and earn $30,000 a year as home-based income. The difference is rarely talent — it's idea selection. When I led product at my old company, we had a saying: "the cost of a bad idea isn't the building, it's the year you spent on the wrong thing." Good news: idea selection is a skill you can learn faster than coding. This lean guide gives you the two real sources of profitable ideas, a fast filter you can run in an afternoon, the validation steps that disprove bad ideas cheaply, and the patterns that consistently sell in the current market.
The Only Two Sources That Reliably Produce Sellable Ideas
Almost every profitable indie iOS app I can name in 2026 — including the ones built by solo devs working from home — came from one of two sources, not from a flash of cleverness.
The first is solving your own problem. The developer hit a real, annoying problem in daily life, looked for an app, didn't find one they liked, and built it. That's the story behind Things, Bear, Day One, and dozens more. The advantage: you understand the problem deeply, you're your own first user, and you can iterate on whether it actually solves the problem.
The second is finding an underserved sub-niche of an existing category. The developer noticed the top apps in a category had blind spots, room to specialize, or low-quality competition, and built a more focused version. That's the story behind dozens of niche wins in fitness, productivity, finance, and parenting. The advantage: you don't have to invent a category, you just have to be better at one specific angle.
The sources to avoid are the seductive ones: "I had a clever idea no one's done" (there's usually a reason no one's done it) and "my friend said this would be useful" (your friend is being polite). Real frustration with existing tools beats cleverness every time. For the next step after you have a candidate, see how to validate an app idea.
Where to Dig for Underserved Niches
The places I've watched indie developers find profitable niches over and over: browse the top 100 in categories you care about and look for apps rated under 4.5 with high review volume — that's demand plus unhappy users, which is opportunity. Read the 1-star reviews of the top apps in a category; every complaint is a feature gap. Search subreddits like r/iOSAppMaker, r/AppHookup, and niche-interest subs for posts asking "is there an app for X" with weak answers. Check Google Trends and an ASO tool like ASOmobile or AppTweak for keywords with high volume but low-quality top results. Lurk in hobby communities — knitting, climbing, model trains, parenting — where people ask for tools that don't exist yet.
Then cross-reference. A niche that appears in App Store research, has frustrated competitors, AND has communities complaining about existing tools is a strong signal. One source alone is a hunch; three overlapping sources is an opportunity. For more on choosing among them, see best app niches 2026.
The Filter Table: Score an Idea Before You Commit a Year
Before committing real time, run every candidate idea through these seven filters. Talk to five potential users for the first one; the rest you can assess from research. An idea passing six or seven is a genuine opportunity; four or fewer is probably not worth the year.
| Filter | The question | Pass signal | | --- | --- | --- | | 1. Real problem | Is this actually annoying for people? | 3 of 5 users say "yeah, that's annoying" before you pitch | | 2. Willingness to pay | Would users pay to solve it? | Recurring problem suited to a subscription, or clear one-time value | | 3. Category access | Is the App Store category winnable? | Reference / Lifestyle / Productivity sub-niches over crowded Photo & Games | | 4. v1 in 3 months | Can you ship a first version fast? | Scope fits a quarter, not a year | | 5. Update story | Can you maintain it without burning out? | Stable scope, not a feature treadmill | | 6. Compliance fit | Does distribution favor a solo dev? | No kids / medical / heavy financial legal load | | 7. 12-month interest | Would you still use it in a year? | You'd genuinely keep it on your home screen |
The table is the whole point of this guide: it turns a vague "is this a good idea?" into a score you can defend. See how to make money with apps for the monetization context behind filter two.
Validate Demand Before You Write Code
The single biggest leverage move in indie app development is validating demand before building. Four methods that work in 2026: build a one-page site explaining the app and run a small $50 to $200 Google or TikTok ad campaign for two weeks tracking waitlist signups — if you can't get signups at $5 each or less, the demand isn't there. Use an ASO tool to check search volume for your target keywords; under 10 US searches per day means the niche is too small to monetize. Study competitors — five dead or uninterested competitors means a dead market, while five thriving with 50,000+ reviews and 4.5+ stars means the market is real. Build a small audience first by posting about your topic on Twitter or TikTok for a few months; if you can't earn 1,000 genuinely interested followers, you won't earn 1,000 paying users.
Validation isn't about proving the idea works; it's about disproving it cheaply if it doesn't. Most ideas that sound good fail validation, and the ones that pass are the ones worth building. For the deep version of this step, see how to validate an app idea.
Patterns That Consistently Sell — and the Ones to Skip
After watching what works in the App Store this year, five patterns consistently produce profitable indie apps. Niche tracking apps — specialized trackers for specific user types ("workout tracker for powerlifters," "food tracker for diabetes," "mood tracker for therapy") consistently produce $5,000 to $50,000/month apps even though the broad category is crowded. Single-purpose utility apps that do one thing exceptionally well (text expander, file converter, specific timer) with premium or one-time pricing and low support burden. Content-rich reference apps that bundle data into an interface (medical reference, cocktail recipes, gardening guides) where the data justifies a subscription. Premium versions of free utilities — beautiful, ad-free, more powerful takes on common free apps. Privacy-focused alternatives to mainstream apps (notes, journal, photo storage) for a steady, growing audience.
Be skeptical of anything that needs viral growth to monetize, complex multi-user social apps from a solo dev, and hardware-dependent apps. The winning patterns share one property: a single user paying once or subscribing covers their own cost without needing virality. Differentiation seals it — "a todo app" isn't differentiated, but "a todo app for parents tracking chores with kids" is. If you can't write a 30-second pitch contrasting your app with the leader, your customers can't either. Avoid the classic mistakes: building for yourself when you're not the user, confusing a feature for an app, assuming high competitor reviews mean a category is closed, and falling in love with the technical challenge instead of the market. Time-box exploration to two to four weeks, then commit — a 7-out-of-10 idea you ship beats a 9-out-of-10 idea you never ship. For what comes next, see best app niches 2026, how to market an iOS app, and the post-idea build workflow in how to build an app with AI. For the official rules that shape which categories a solo dev can realistically ship in, Apple's developer hub is the source of truth: Apple App Store for developers.
Frequently asked questions
Real questions from readers and search data — answered directly.
Do I need an original idea or can I clone an existing app?
How do I know if my idea is too small a niche?
How long should I spend researching before building?
Can AI help me find app ideas?
Should I build the app I want to use or the app the market wants?
What's the most common reason indie apps fail?
Keep reading
Related guides on the same path.