OOmnistu

Blog / Mobile App Development

Mobile App Development

Ratings prompts that work: in-app review APIs, quotas and the right moment

Both stores show native rating sheets with strict quotas - Google bans pre-questions like 'Do you like the app?' - so the prompt's timing and cooldown decide everything.

OOmnistu
Reviewed 2026-11-19 · 3 min read

A well-timed ratings prompt lifts your store rating; a badly timed one teaches users to tap "not now" forever. Both stores now offer native in-app review APIs that show the rating sheet without sending the user away - and both wrap that API in rules that punish lazy prompting. This guide covers what the official documentation actually allows and how to choose the moment.

Google Play: the In-App Review API and its quota

Google Play's In-App Review API lets users submit a Play Store rating and review without leaving your app. The flow can be triggered at any point in the user journey, but Google enforces a time-bound quota on how often the dialog can be shown: calling launchReviewFlow repeatedly in a short period (Google's example is less than a month) may silently show nothing. Design your trigger so a no-op is harmless - never build UI that assumes the sheet appears.

Google's guidance is equally specific about what not to do around the prompt: your app should not ask the user any questions before or while presenting the rating card - no "Do you like the app?" gates and no predictive questions. The intent is that the rating dialog is not a filter that routes happy users to the store and unhappy users to a private form. Follow it; reviewers and users both notice.

Apple: requestReview and its limits

On iOS, StoreKit's review request shows the system's rating sheet, and Apple is precise about the limits: the system displays the prompt a maximum of three times within a 365-day period, people can disable review requests on their device entirely, and Apple's best practices say to avoid showing a request immediately at launch and to avoid requesting a review as the result of a user action. So the same rule applies: pick the moment carefully and treat a non-appearance as normal - with three chances a year, the quota is the strategy.

Choosing the moment

The mechanics are identical across stores: prompt after a completed success, not at launch, not mid-task and not after an error. Good triggers are moments of delivered value - the third finished workout, a completed order, a level passed. Bad triggers are app open number two, purchase confirmations for anything the user has not yet received, and any moment you would find it annoying yourself.

Because both stores quota the prompt, add a local cooldown (for example, at most one request per 60 days, and never again after the user has rated) so you spend the quota on genuinely good moments rather than burning it on an early, mediocre one. And never gate features or rewards on leaving a review: incentivised ratings violate both stores' policies.

Ratings are a loop, not a campaign

The prompt gets the rating; what you do next keeps it. Watch updated ratings over time - both consoles show how users change their reviews after you fix issues - and treat a dip after each release as a release-quality signal, not a marketing problem. The teams with durable 4.5+ ratings are the ones whose prompts fire at genuinely happy moments and whose crash-free rate gives users nothing to complain about.

Sources

Prepared with AI assistance and reviewed before publication. Play quota and prompting rules are paraphrased from Google's documentation checked on 19 November 2026; the 60-day cooldown is an editorial example, not a store requirement. Apple behaviour is described from Apple's StoreKit documentation.