Two things happened to me in the same week, and they turned out to be the same fact.
The first: a developer in r/AppBusiness asked how to get from 10 downloads to 100. In the comments someone asked where his first ten came from, and he answered honestly — two were him and the friend he built the app with, the other eight came from friends they recommended it to.
So the real number wasn't ten. It was zero. Ten installs, zero strangers.
The second: I was pulling recent reviews for a different reason and happened to look at Headspace's newest 50 US App Store reviews. 35 of them were one or two stars.
Ten installs, zero strangers, and a meditation app with close to a million ratings sitting there publishing its weaknesses in public, for free, every day. If you are early, the second number is your research budget and the first one is not.
What friends can and cannot tell you
Friends are not useless. They are just answering a different question than the one you are asking.
They can tell you: the app crashes on a Pixel 6, the onboarding has a dead end at step three, the paywall appears before anything useful happens. Those are real bugs and you should fix them. Friends are also the only people who will actually tell you, because they like you.
What they cannot tell you is whether a stranger understands the app, because they arrived with the explanation already attached. You told them what it does before they installed it. They are not confused at the point where real users get confused — they are rooting for you. Their install is a favour, and a favour is not a data point.
This is why "I got 10 downloads, how do I get 100" is not a distribution question yet. Going from 10 to 100 through the same channel — friends, then friends of friends — produces a bigger number and the same blind spot. You would be scaling a sample that knows too much.
The signal that already exists
Here is the part people skip. Your category's strangers have already told you what they want, in the one place they have no reason to be polite.
I pulled Headspace's newest 50 US App Store reviews on 10 November 2026. The window they covered was 3 September to 8 November — about nine weeks. Of those 50, 35 were 1–2 star (29 one-star, 6 two-star). I read all 35 and put each one in a single primary bucket:
| Primary complaint | Reviews |
|---|---|
| Paywall — "you can't use anything without paying" | 8 |
| Billing friction — trial auto-charge, cancellation that doesn't cancel, "still billed" | 5 |
| Feature creep — "not the app it used to be", "stop inventing features" | 5 |
| AI — "why is Headspace pushing AI", "AI meditation coach? Nope" | 5 |
| Navigation and clutter — "can't find what I need", "terrible navigation" | 5 |
| Content depth — sessions too short, nothing over 20 minutes | 2 |
| Everything else — one bug, one slow launch, one missing dark icon, one bad therapy referral | 5 |
That is one app, one page of the feed, one person's reading. It is not a sentiment model and it is not a market study. But look at what it gives you if you were about to launch a meditation app this month.
Four of those buckets are not bugs. They are decisions the incumbent made and cannot cheaply reverse:
- A subscription model that gates almost everything is not going to be un-gated; it is the business.
- An AI coach direction is a company bet, not a toggle.
- A content library that grew by accretion and is now hard to navigate will stay hard to navigate.
- Trial and cancellation friction exists because it works financially.
A bug gets fixed in the next release. A strategy doesn't. The complaints that survive for years are the ones written by a business model, and those are the ones a new app can stand on.
That is your subtitle. Not "meditation made simple" — everyone says that. Something like "meditation without the AI coach, and a free tier that actually plays something". It is one line, it is checkable before install, and it came from 35 people who have no idea you exist.
Doing it on your own category
The mechanics are boring, which is the point:
- Pick the three apps your users are most likely to come from. Not the category leaders in the abstract — the ones a person would have installed before they install yours.
- Read their newest reviews, filtered to one and two stars, and fix the date window before you start counting. Fifty reviews is a week for a big app and two years for a small one, and a complaint about a version that no longer ships will poison everything downstream. (I wrote about that trap separately: your review sample is not a time unit.)
- Read for one sentence shape: "I stopped because __", "I left when _", "I'd pay for it if it just __". Not for sentiment, not for star averages. You are collecting the sentences people use when they leave.
- Put each review in one bucket, by what the person is actually angry about. Six to eight buckets is normal at this size. If you get twenty, your buckets are too fine.
- Cross out every bucket that is a bug or a single person's preference. What is left is either a structural constraint of the incumbent or noise.
If the buckets look like the table above — a handful of structural complaints, each with five to ten people behind it — you now have better evidence about your positioning than a hundred friend installs would give you, and you have it before you have users.
If you want the longer version of steps 1–4, the competitor review guide walks through it page by page. If what you are hunting is a missing feature rather than a missing feature-set, the feature request guide is the sharper lens.
Two filters, or this becomes a roadmap you shouldn't build
Filter one: is this person your user? "Bring back the 2016 version" is a complaint from someone who wants a product that no longer exists. You cannot win them and you should not try. What you want is the person who is still trying to do the job and failing.
Filter two: can you actually be different there, or just claim it? A paywall complaint is not an invitation to build a free app with no business model. It is an invitation to be honest about what is free — which is a much smaller promise, and one you can keep. If your app can't survive making that true, it is not your wedge.
One limitation worth saying out loud
This only works if you can get the reviews. Apple's public review feed is inconsistent: when I pulled the apps for this piece, most returned an empty feed and only a couple returned their newest 50. The store pages, Google Play, and any tool that reads them will get you there; the point is to fix the window, state the source, and not pretend a scrape is a census.
If you want the mechanical version, this is what I built ReviewFold to do — reviews in, a report out, with the source review behind each finding, so you can check the claim instead of trusting the summary. You can also do it by hand with a spreadsheet and an evening, and I would rather you did it by hand this week than waited for a tool.
Either way: your first ten installs are a favour. Their reviews are evidence.
Disclosure: I work on ReviewFold, which analyzes app reviews. The Headspace numbers above come from Apple's public US App Store review feed, pulled on 10 November 2026 (50 newest reviews, 3 September – 8 November); they are one storefront, one sort order and one snapshot, not a market study. AI assistance was used for editing; the review counts and the date window were read from the feed directly.
Top comments (0)