App store review prompts: when to actually ask them

Most studios treat the in-app review prompt as a minor implementation detail — call the native API somewhere convenient, ship it, move on. That treatment ignores a hard technical constraint that changes the entire strategy: the platform-native review prompt is capped at a small number of appearances per app per year, and Android's equivalent doesn't guarantee the dialog shows every time you request it either. You don't get to decide whether to ask. You get to decide which of a small number of chances to spend, and on what moment.

The constraint that changes the question

Once you know you have a handful of tries, not an unlimited number, the question stops being "should I prompt here" and becomes "is this the best moment available to me this year." A prompt fired at a mediocre moment doesn't just fail to convert — it spends one of your limited chances on a player who might have rated five stars if you'd waited for a better moment, or worse, on a player who was having a bad session and now associates the interruption with frustration instead of satisfaction.

This reframes review prompting from a feature you build once into a resource-allocation decision your live-ops or growth function should be actively managing, the same way you'd manage a scarce, high-value ad placement rather than a routine notification.

The moments that convert, and the ones that burn a prompt for nothing

The consistent pattern across studios that get this right is timing the ask to a moment of demonstrated positive affect — right after a level completion, a milestone unlock, or a purchase the player chose to make and clearly got value from. These are moments where the player has just had a good experience and is, briefly, in the best possible frame of mind to say so publicly.

The moments to avoid are just as consistent: right after a crash or an error, mid-task where the prompt interrupts something the player is trying to finish, and anywhere inside onboarding, before a player has had enough of the game to have an informed opinion about it. A prompt fired during onboarding isn't just a wasted chance — it risks a genuinely negative response from someone who hasn't seen enough of the game to rate it fairly, and that response is exactly as permanent and exactly as capped as a good one would have been.

The pre-prompt filter

The pattern that consistently outperforms firing the native prompt directly is asking a soft, in-house question first — something as simple as "enjoying the game so far?" with a yes/no choice, shown through your own UI rather than the platform's. A player who says yes gets routed to the native prompt, spending one of your limited chances on someone who's already told you they're positive. A player who says no gets routed to a private feedback form instead, which does two things a direct native prompt can't: it protects your scarce prompt budget from a response you already knew would be negative, and it captures the actual complaint, which a one-star public review never gives you in useful detail.

This filter isn't gaming the review system — nothing about it changes what happens after a player chooses to go to the store, and a player who says yes and then decides not to follow through loses you nothing you wouldn't have lost with a direct prompt. It's simply not spending a scarce resource on a response you can already predict.

Frequency and session-count gating

Beyond picking the right moment, the studios that get consistent results also gate on how much history a player has with the app before ever asking. A player who's opened the app three or more times has already told you, through that repeated behavior, that they don't dislike the game enough to have stopped — which makes them a materially better candidate for a positive review than someone on their first or second session, however good that particular session happened to be. Combining a minimum session count with the positive-affect-moment timing, and respecting a real minimum gap before asking again even a player who dismissed the soft in-house question, is what turns review prompting from a one-off feature into a system that compounds.

What this connects to

A review prompt fired at the right moment doesn't just produce a review — it's one input into the same store-listing conversion loop as your screenshots, your description, and your store-page creative, all of which gamemantra's dashboard treats as connected surfaces rather than separate checklists. Rating volume and rating quality feed directly into how a new visitor reads your store page before they've played a single second of your game, which is exactly the audience a well-timed prompt is quietly working on your behalf to win over.