Test your in-app rating prompt before launch
· 7 min read
Ratings are what people read before they install. So you add the "Rate this app" prompt, and then you can't tell if it works. It never shows in TestFlight. It shows every single time in development. Google's dialog may not appear at all. Or it works, but it fires on first launch, or right after an error. This post covers what Apple and Google document about both prompts, how to test each one, and a test task you can give testers. I checked the official pages in November 2026.
Short answer: use the system prompt on each platform, ask after a success moment, never from a button, and test it in the right build. Development builds on iOS always show it. TestFlight never does. On Android you test with an internal test track.
iOS: what the prompt does
The API is requestReview. Apple's RequestReviewAction page says it asks the user to rate or review your app "if appropriate". Your call is a request, not an order. The page says "App Store policy governs the actual display of a rating and review request view".
The page lists the limits. If the person has not rated or reviewed your app on this device:
- StoreKit shows the request "a maximum of three times within a 365-day period".
- If they already rated it, a new request needs a new app version and more than 365 days since the last review.
Apple's Ratings and reviews guidelines add that people "can also opt out of receiving these prompts for all apps they have installed". So a missing prompt is not always a bug.
Development and TestFlight
This part confuses people. The Apple page says that in development mode, "StoreKit always displays the rating and review request view, so you can test the user interface and experience". Then it says "this method has no effect in apps that you distribute for beta testing using TestFlight". So in TestFlight, a silent prompt is normal.
The same page has one more rule. "Because this API may not present an alert, don’t call it in response to a button tap or other user action." A "Rate us" button is better as a link to your App Store page. The page suggests adding action=write-review to the product page URL.
Android: the In-App Review API
Google's in-app review guide describes a quota. Google Play enforces "a time-bound quota on how often a user can be shown the review dialog". Calling launchReviewFlow more than once in a short time "might not always display a dialog". It also says "The specific value of the quota is an implementation detail", so Google can change it without notice.
The guide gives the same button advice as Apple: "you should not have a call-to-action option (such as a button) to trigger the API". A user may have used up their quota, "presenting a broken experience". For a button, it says to redirect the user to the Play Store instead.
How to test on Android
The test in-app reviews page says you can test "using either internal test tracks or internal app sharing". With an internal test track:
- The account must be a tester on the internal track, and the primary account in the Play Store.
- It must have downloaded the app from the Play Store, so the app is in its library.
- It must not already have a review for the app.
- "The quota limits are not enforced if the app is downloaded from the internal test track."
With internal app sharing, "reviews can't be submitted", and the button is disabled. That is expected.
FakeReviewManager is for code tests. The page says it "does not simulate the UI". It only returns a fake success. Use it to check that your app carries on after the flow ends.
If the dialog does not show, the page's troubleshooting table lists more causes, such as an enterprise account or a sideloaded Play Store. For an existing review it says "Delete the review directly from Play Store."
For setting up the track, see internal, closed and open testing on Google Play. For TestFlight, see TestFlight external testers and the public link.
What the rules forbid
I read both stores' rules, because a prompt that breaks them can get your app rejected or removed.
- Apple's App Review Guidelines, guideline 5.6.1: "Use the provided API to prompt users to review your app" and "we will disallow custom review prompts". So no home-made "Do you like our app?" screen.
- The same guidelines, under 3.2.2: "Apps must not force users to rate the app, review the app, download other apps, or other store-related actions in order to access functionality, content, or use of the app."
- Apple also warns that if you "inflate your chart rankings with paid, incentivized, filtered, or fake feedback", it may take steps that include expelling you from the Apple Developer Program.
- Google's ratings and reviews policy says "We prohibit any manipulation of ratings, reviews, or install counts. This includes incentivizing feedback". Its table says "Don't offer rewards or incentives for ratings or reviews."
- The Android guide adds that your app "shouldn't ask the user any questions before or while presenting the rating button or card", including "Do you like the app?". That is a happy-user filter, and it is not allowed.
When to ask
Both stores say the same thing in different words. Apple's guidelines say to "Ask for a rating only after people have demonstrated engagement with your app or game", such as completing a level or a significant task. They say to "Avoid asking for a rating on first launch or during onboarding" and to "Avoid interrupting people while they’re performing a task or playing a game". They suggest "at least a week or two between requests". Google says to trigger the flow "after a user has experienced enough of your app or game to provide useful feedback".
My own rule on top: ask right after something went well, like an export that finished. Never after an error.
How to test it
- Xcode or a development build. You will see the prompt every time. Check where it fires and that nothing is covered or blocked.
- TestFlight. No prompt. Check that your app works as normal, with no crash and no stuck screen.
- Play internal test track. You may see the dialog. Check the account conditions above, then check the timing.
- Internal app sharing. The dialog may show, but you can't submit.
- Production. Both stores decide. Never rely on the prompt appearing. Check that no screen waits for it.
The last check matters most. Call the API, then carry on as if nothing happened. For tasks like this, see how to write a test task, and for your store page, see the App Store product page for a first app.
A test task testers can follow
Paste this into your test task and change the first line.
Do the main task: [your task].
Stop when it succeeds.
Did a rating prompt appear?
- If yes: when? Did it cover
anything or block a tap?
- If no: just say "no prompt".
Was it ever shown at a bad time
(first launch, after an error,
mid-task)?
Send: phone model + OS version,
and how you got the app
(TestFlight / Play link).On TestFlight, "no prompt" is the right answer. Use this task mainly on Android tracks.
Where TestSwap fits
TestSwap is a free app testing exchange where indie developers test each other's apps. You can post web, iOS and Android apps, with a link testers can open or install, like a TestFlight link or a Google Play testing link. You can add a test login, which only signed-in testers can see. Everyone starts with 3 credits. Writing a review earns 1, and each review your app receives costs 1. You can rate each review 👍 or 👎, and a 👎 takes back the reviewer's credit.
One thing to be clear about. A TestSwap review is private feedback for you, the maker. It is not an App Store or Google Play rating. Do not ask testers to leave a store rating in return for a review or a credit. Both stores' rules above forbid incentives for ratings. Ask them what they saw instead. TestSwap is not affiliated with Apple or Google.
The checklist
- Use
requestReviewon iOS and the In-App Review API on Android, not a custom screen. - Ask after a success moment, never on first launch or onboarding, and never after an error.
- Never call the API from a button. Link to the store page instead.
- Don't ask "Do you like the app?" before the prompt.
- Don't offer rewards for ratings, and don't make users rate to use the app.
- Check the prompt in a development build, and expect nothing in TestFlight.
- On Android, test with an internal test track account that has the app in its library.
- Check the app works whether the prompt shows or not.
- Ask testers when it appeared and whether it got in the way.
Try it
Put the prompt where users have just succeeded. Then post your app on TestSwap with the test task above. Reviewing someone else's app first is the quickest way to see how it works. Tell me what's missing or broken (@dizid on X).