It's one of the most common startup post-mortems: not bad execution, not bad marketing — nobody wanted it. The good news is that almost every part of “nobody wanted it” is checkable in advance, using signals that already exist in public app store data. You don't need a survey, a focus group, or a working prototype to get a real answer. You need to know where to look.
- Check whether apps like yours already exist — and whether that's a good or bad sign.
- Read what real users already complain about in the closest competing apps.
- Size the market roughly (TAM/SAM/SOM) so you know if it's worth the effort.
- Check whether real search demand for the category is growing, flat, or fading.
- Make the call: build as scoped, narrow the idea, or pass — before you write code.
Step 1: Check whether the market already exists
Before anything else, find out who's already solving this problem. Search the App Store and Google Play for the closest existing apps to your idea — not just the obvious market leader, but the smaller, newer entrants too.
Here's the counterintuitive part: finding nothing similar isn't automatically good news. In consumer software, a total absence of competitors more often means there's no proven demand than that you've found untapped gold. Finding several apps already doing something like your idea is usually the healthier signal — it means people are already searching for this, downloading things for this, and paying for this. Your job shifts from “does this market exist” to “where's the gap in how it's currently served.”
Point Appifacts at the closest existing app to your idea and its Market Insights & Demand Forecast module gives you a real read on competitive pressure — how many serious competitors exist, how many new entrants showed up in the last year, and whether the category is described as crowded or wide open.
Step 2: Read what people already complain about
The fastest, cheapest validation signal available to you isn't a survey — it's the public reviews of the closest existing app to your idea. Nobody fills out a form to complain about software they don't use; a one-star review is unpaid, unprompted, real frustration from someone who cared enough to use the app and then write about why it let them down.
Read through the last month or two of reviews for your closest competitor and look for repetition. One person complaining about a missing feature is an anecdote. Twenty people independently describing the same gap — in their own words, across both the App Store and Google Play — is a validated problem with a specific, buildable angle.
The App Reviews module pulls the last 50 real reviews per platform for any app, summarizes recurring themes into concrete advantages and disadvantages, and closes with a plain-language read on what gap the negative reviews leave open for a competing app — the exact signal this step is looking for, without reading 200 reviews by hand.
Step 3: Size the actual opportunity
A validated problem isn't automatically a validated business. Before committing months to an MVP, get a rough sense of scale: how big is the total addressable market (TAM), how much of it can you realistically reach (SAM), and what slice could you plausibly capture in year one (SOM)? None of these need to be precise — they need to be roughly the right order of magnitude.
A market sized in the tens of millions of dollars with a handful of well-funded incumbents is a very different bet than one sized in the low billions with fragmented, mediocre competitors. Knowing which one you're in changes how much runway, differentiation, and patience the idea actually needs.
The same Market Insights module estimates TAM/SAM/SOM, a demand score, and growth drivers directly from a comparable app's category and profile — clearly labeled as an AI estimate, not measured fact, but a reasonable first draft to sanity-check your own assumptions against.
Step 4: Check whether real demand is growing, flat, or fading
A market can look attractive on paper and still be shrinking in practice. Check actual search interest for the category over the last 12 months — is it climbing, flat, or in decline? A merely-decent idea in a category growing 20-30% a year is a far more forgiving bet than an excellent idea in a category that peaked two years ago.
This step also surfaces timing: many categories have real seasonality (fitness apps every January, event apps every spring and holiday season), and launching a few months ahead of a predictable demand peak is a free advantage most first-time founders leave on the table.
The Google Trends module shows real 12-month search-interest data for a comparable app, interpreted for momentum and seasonality, plus a short-term forecast clearly separated from what's actually observed.
Step 5: Make the call — build, narrow, or pass
With a competitive read, a real complaint to solve, a rough market size, and a demand trend in hand, the decision is rarely a flat yes or no. Most ideas land in one of three places: build it roughly as scoped, narrow it to the specific wedge the data actually supports, or shelve it until a signal changes.
The goal of this whole exercise isn't certainty — nothing before real users touch a product is certain. It's replacing a guess with a grounded opinion you can defend, revisit, and act on quickly, instead of discovering the same information the hard way six months and a lot of engineering time later.
The Build Recommendations module synthesizes everything above — positioning, keywords, market data, search reputation, and real review gaps — into a verdict, a difficulty-to-compete score, and a scoped MVP feature list, so the “build, narrow, or pass” decision starts from a full picture instead of a hunch.
See it end to end
Every step above maps to a real module in an Appifacts report — not a separate tool per step, one search that runs all of them in parallel. The use cases below show the full output on real apps, module by module: