Quick answer
Ask users for a rating after a positive moment using the official in-app review prompt, never in exchange for rewards and never only to happy users. Reply to reviews, fix the issues people mention, and test on real devices before release so fewer problems reach the store. Consistent quality produces consistent genuine reviews.
Start with an app worth reviewing
Most low ratings are about the same few things: crashes, slow loading, login and OTP problems, aggressive ads, and features that don't work on a particular phone. Before you think about asking for reviews, make sure those basics are solid on the devices your users actually have.
Real-user testing is the fastest way to find these issues. Testers on a spread of Android versions and manufacturers will find the crash on a budget phone that your development devices never showed. See Mobile App Testing and our pre-launch testing checklist.
Use the official in-app review prompt
Google Play offers the In-App Review API, and Apple offers a similar prompt. They let users rate without leaving your app. Follow the platform guidelines:
- Trigger the prompt after a user has experienced value — finishing a task, reaching a level, completing an order.
- Don't show it at first launch or in the middle of a task.
- Don't ask "Do you like our app?" first and only show the prompt to people who say yes. That kind of filtering is not allowed.
- Don't put a "Rate us 5 stars" button that calls the API, and don't change or cover the prompt.
- Remember the platform limits how often the prompt appears, so call it at meaningful moments.
Things that break policy
| Don't | Why |
|---|---|
| Offer coins, discounts or features for a rating | Incentivised ratings are prohibited |
| Buy reviews or use rating services | Manipulation; risks app removal |
| Ask testers to post public ratings | Testing feedback must stay private |
| Send only happy users to the store | Gating reviews is not allowed |
| Ask staff or friends for reviews | Conflict of interest |
Reply to reviews — it changes ratings
Replying shows future users you care, and many users update their rating when you fix their problem. Keep replies short and specific:
- Thank the user and mention what they liked.
- For problems, apologise, ask for details through support, and say when a fix is coming.
- After you ship a fix, reply again so the user knows.
Build a steady feedback loop
- Collect private feedback inside the app (a simple "Send feedback" option) so frustrated users have somewhere to go besides a one-star review.
- Group reviews and feedback into themes every week.
- Fix the biggest theme first, then say so in release notes.
- Before each major release, run a short real-user test on the changed features.
This loop is slower than buying a batch of stars, but it compounds. Read bought reviews vs real tester feedback for the full comparison.
Frequently asked questions
When is the best time to ask for a review?
Right after a user completes something meaningful and positive in your app. Avoid the first session, error screens and moments when the user is in a hurry.
Can I remind users to review in a newsletter?
Yes, a neutral request to share their experience is fine, as long as it goes to all users and doesn't offer a reward or ask only for positive reviews.
Do replies to reviews affect ranking?
Replies mainly affect how users see your app and whether they update their rating. Better ratings and conversion can help over time.