How to Get Your First Reviews Without Buying Them
Reviews are the one part of a listing you cannot write yourself. When to ask so the prompt is not wasted, what both stores forbid, why review-gating backfires, and how to get the first few from people who already talked to you.
Every other part of a listing is something you write. The title, the screenshots, the description — you control all of it, which is exactly why a careful reader discounts all of it. Reviews are the one asset you cannot produce yourself, and that is the entire reason they carry weight.
Which is awkward when you have none, because the fastest way to get reviews is to already have users, and one of the things that gets you users is having reviews. This is how to break into that loop honestly, starting from zero.
Reviews do two jobs and only one of them is visible
The obvious job is social proof at the moment of decision — the number sitting next to your name while somebody decides whether to spend a minute on you.
The second job is slower and matters more. Both stores show ratings in results and both treat them as one of the inputs deciding what gets surfaced at all. Social proof helps the people who already found you. The ranking effect compounds, and it is the reason a listing with reviews keeps getting easier to find while one without stays invisible.
Your prompt is not broken, your timing is
People do not rate your app. They rate the last thing that happened in it. Ask immediately after something went wrong and you get a one-star review about that specific thing, permanently attached to your listing.
Ask after one of these:
- A session that went well — a level finished, a run completed, a personal best.
- The third or fourth return visit, when the habit is real and not curiosity.
- The moment the thing they installed it for actually worked for the first time.
- After you shipped a fix for something they told you about.
Never ask after one of these:
- First launch, before anything has happened worth rating.
- Immediately after a crash, an error, or a failed sync.
- Directly after a paywall, a price, or a permissions request.
- In the middle of a task, where the prompt is purely an interruption.
That single change — moving the trigger from a timer to a success — does more than everything else in this article combined.
Use the platform's own prompt
Both platforms ship an in-app review API, and it is strictly better than a custom popup. The review gets written and submitted without the person leaving your app, which removes the trip to the store that most people never come back from.
It also means the system decides when the prompt actually appears, and it limits how often. That constraint cuts both ways: you cannot nag, and a prompt spent at a bad moment is genuinely spent. Read the current documentation for your platform before wiring it up, because the details change and the behaviour is not identical across the two.
Do not build a filter
The pattern is everywhere: ask "are you enjoying the app?" first, send the people who say yes to the review prompt, and route the people who say no to a support form instead.
Store guidelines on this have tightened over time and you should read the current ones before shipping it. But the product argument stands on its own, whatever the rules say this year:
- It hides the exact feedback you most need, from the users most motivated to give it.
- Your rating stops describing your app and starts describing your filter, so you can no longer use it to tell whether anything you shipped worked.
- Readers are not stupid. A wall of five stars with no substance reads as managed, and managed reads as worse than a real 4.1.
If somebody is unhappy, the fix is to ask them why and then fix it — not to route them away from the one place their opinion would have cost you something.
What you cannot do at all
- Pay for reviews. Both stores prohibit it, both look for it, and the penalty lands on your app rather than on whoever sold them to you.
- Trade anything for one. Currency, an unlock, a discount, entry to a draw — all the same category, whether or not you ask for five stars specifically.
- Post them yourself. Friends and family writing as strangers is the version people convince themselves is fine. It is the same thing, and it reads like it.
Beyond enforcement, bought reviews are simply obvious. Forty variations of "Great app!!! Love it!!!" posted in one week tell a careful reader precisely what happened, and the careful readers are the ones who were going to install.
Ask the people who already talked to you
Your first ten reviews are not going to come from strangers. They come from the small number of people who have already made contact: anyone who emailed support, replied to a post, reported a bug, or answered a question in a community thread.
These people are far more likely to write something specific and useful, because they have already demonstrated they care enough to type. The ask that works is a one-line reply to a conversation already in progress, after you have done something for them — you fixed their bug, so you tell them it shipped, and mention that a review would genuinely help. Individually, in the thread you were already in. Not a template, not a mailing list, not a push notification.
If nobody has ever contacted you, that is a finding rather than a setback: it means the work right now is the diagnosis in why nobody is downloading your indie game, not the review count.
Reply to every review you get
Public replies are read overwhelmingly by people who will never write a review themselves. A calm, specific answer to a two-star — what happened, what you changed, when it ships — does more for the next reader than the two-star costs you. It is the only place on your listing where a stranger sees how you behave rather than how you market.
People also update reviews after a fix, but only if they find out there was one.
Reviews the stores do not own
Store reviews have one structural weakness: they live inside the store app, where search engines cannot read them. A review on a public web page is one a search engine can index, which means it works for you in a channel your store listing never touches.
That is the case for having a page outside the stores — a community thread, a forum post, a directory listing — and it is worth being explicit that the directory here is one of those, so treat this as an interested party talking. A review on the board is worth 12 points, an upvote 10, and a comment 4, plus a rating bonus that grows with how many reviews stand behind it — which is deliberately built so a single five-star from a friend barely moves anything. The formula is published because a ranking you cannot audit is just an advert.
What to do this week
- Move your review prompt from wherever it is now to a success moment.
- If you built a filter, delete it, and read your one-stars instead.
- Reply to every review currently sitting on your listing, including the old ones.
- Message the people who have already contacted you, individually, and only where you have actually done something for them.
- Make sure the thing they would be reviewing is worth it — the listing checks are in the press kit guide.
None of this is fast. Reviews accumulate at the speed of people genuinely using the thing, which is the property that makes them worth having in the first place. If you want a page where they are public, crawlable, and start from zero, put it on the board.