AppReviewX Log in

All guides

When to ask for app reviews: the right moment, the right user

· 4 min read

Ratings and reviews shape how many people install your app. The honest way to get more of them is to ask real users at a good moment and make it easy. This article is about timing: when a prompt appears and to whom. Where it sits on the screen and what it looks like is covered in how a rating prompt should look and where to place it.

A reminder before anything else: never offer rewards for ratings, never buy or trade reviews, and never ask only happy users to rate. Store rules prohibit manipulating ratings, and it damages trust. Check the current policies of Google Play and the App Store before you ship a prompt.

The principle: ask after a win

People are most willing to rate when they have just got value from the app. Poor timing, such as at launch, during an error or in the middle of a task, produces annoyed dismissals and sometimes a bad review that is really about the interruption.

Good moments are things the user would call a success:

Bad moments:

Use thresholds, not luck

Combine a few conditions so the prompt appears only for engaged users:

  1. Minimum usage. For example, the app has been opened on at least three different days.
  2. A success event in this session.
  3. No recent problems. No crash, error or failed payment in the last session or two.
  4. Not asked recently. Keep a timestamp and wait weeks between asks.

Tune the numbers to your app. A meditation app and a tax app have very different natural rhythms.

Respect the platform limits

Both platforms provide a native review dialog that you should use rather than build your own sheet that imitates it:

Because the system can ignore the request, never tie the prompt to a button like "Rate us" that must do something. Use a separate link in settings that opens the store page for anyone who wants to rate on purpose.

Do not gate by sentiment in ways that break rules

A popular pattern is a pre-question, "Are you enjoying the app?", with happy users sent to the store and unhappy ones to a feedback form. Policies around this change and have been interpreted differently; the safest approach is:

If you want the benefit of catching problems early, collect feedback first on your own channel, from testers, before release. That is what a feedback exchange is for. See how to ask users for feedback without nagging.

Measure what happens

If the average rating drops after a change, the prompt is probably appearing at a wrong moment. Move it later or narrow the conditions.

Checklist

  1. Choose one or two success events.
  2. Require a few days of use and no recent errors.
  3. Wait weeks between asks.
  4. Use the native review dialog only.
  5. Add a separate "rate the app" link in settings.
  6. Offer private feedback to everyone.
  7. Never reward ratings.
  8. Review results monthly.

Need testers for your app? Open a test group on AppReviewX. Start free

More guides