How to Get More Genuine App Reviews, Within the Rules

Both stores give you exactly one sanctioned way to ask for a rating inside the app, and both throttle it without telling you when. The developers who get a steady flow of genuine reviews are not the ones who ask most often; they are the ones who ask once, at the right second, and never try to filter who sees the prompt.

What developers are asking

The question of the year on r/iOSProgramming was prompted by a 9to5Mac piece arguing that a four-star review now functions as a negative one, because ranking and featuring favour five-star averages and a 4 drags a 4.1 down ¹⁵. The follow-up thread asked what the rules actually are: is the "do you love the app?" pre-screen allowed, and does a "Rate this app" button in Settings count as a banned custom prompt ⁷? A second thread came from a developer who received a Guideline 5.6.3 rejection for showing the rating prompt during onboarding, two months and ten updates after launch; the replies were unsympathetic ("why would you ever have a rating request in onboarding?") but confirmed Apple is now enforcing this on existing apps ⁸. On the Android side, a developer with roughly a million monthly users reported that the Play review dialog silently stopped appearing on April 21, 2026, dropping them from about 70 reviews a day to about 10, and wondered whether their "pre-review" sentiment screen had got the app flagged ¹⁰. And in r/IndieDev the perennial question of how to get the first 50 ratings without faking anything got the blunt answer that they come from personally onboarding 50 users and asking at the moment each one gets value ¹².

The prompt APIs and their limits

On iOS the API is AppStore.requestReview(in:) for UIKit and the requestReview environment action in SwiftUI; the older SKStoreReviewController still works but is the legacy path ³. Apple states the system shows the prompt at most three times per 365-day period per app, decides on its own whether a given call displays anything, and recommends calling it after the user completes an action, level or task, never in the middle of one ¹. The prompt shows during development so you can test it but Submit is disabled there ³. Two community notes: on iOS 26.1 the "Not Now" button was disabled on the dialog until a star was tapped, a bug developers confirmed on device and reported fixed in 26.2 ¹¹; and because the three displays are silent no-ops after the cap, the mental model that works is "I get three a year, when do I spend them?" ⁷.

On Android the API is ReviewManager.requestReviewFlow() followed by launchReviewFlow() from the Play Core library ⁴. Google does not publish the quota; it says calling the flow more than once in a short period, "for example, less than a month", may show nothing, and that the value can change without notice ⁴. The API never tells you whether the dialog appeared or whether a review was submitted, so you cannot build logic on the result ^4,5. Quota is not enforced on the internal test track, which is the right place to test; internal app sharing shows the dialog but cannot submit ⁵. Developers who treat both platforms the same settle on one trigger with a long cooldown, such as every four months, or once a month and let Google decide ^10,16.

When to ask

The agreed answer across threads is the "wow" moment: the first point on the critical path where the app has visibly delivered value ^9,13. Jacob Bartlett's two examples are a questionnaire app that prompted five seconds into the results animation and averaged 4.8 stars, and a flight-tracking app that prompted 20 seconds after launch, once its three-second time-to-value had passed, and averaged 4.9 ¹³. A developer building a productivity app proposed a filter of seven days since install, fifteen completed actions and three sessions in the past week, with a 90-day cooldown; the best-received reply agreed that users with a week of use and 10 to 20 actions respond far better than new users, and that post-action prompts beat launch-time prompts because the user is in a good mood ⁹.

Do not prompt in onboarding, on first launch, or after a failure state. Apple's enforcement in 2026 treats an onboarding prompt as a Code of Conduct issue ⁸, and users in the same thread said an app that asks before they reach the home screen is an immediate uninstall ⁸.

In-app review versus a store deep link

The native prompt lets the user rate without leaving the app and is the only mechanism Apple allows for an unsolicited ask; Guideline 5.6.1 says custom review prompts are disallowed ². A link that opens your App Store page with action=write-review is still acceptable when the user chooses it, for example a "Rate this app" row in Settings or an About screen, because it is not a prompt ⁷. On Android, a Play Store link with market://details?id= works the same way and is what Google recommends instead of a button that calls the in-app API, since a button hitting the quota produces a dead tap ⁴.

Sentiment gating, the "Enjoying the app? Yes / No" screen that only shows the real prompt to the happy half, sits in a grey zone that is getting darker. Google's design guidelines explicitly forbid asking any question before or while the review card is shown ⁴. Apple's text is vaguer, but the strongest reading in the community is that a flow whose outcome depends on the user's stated sentiment is a custom prompt ⁷, and the Android developer whose dialog vanished suspected exactly that trick ¹⁰.

Incentives that are banned

Google's policy is the clearest: no rewards, discounts or other incentives for ratings or reviews, no fake or paid reviews, no forced or deceptive prompts, and no encouraging reviews that contain coupons, codes or links ⁶. Apple's Guideline 3.2.2(x) bans making any functionality conditional on rating or reviewing, and the Code of Conduct puts review manipulation alongside chart manipulation as grounds for expulsion from the Developer Program ². In practice this rules out "rate us to unlock", "five stars for a free month", review contests, and recruiting friends to post five-stars to dilute a bad one ².

What developers report as conversion rates

Hard numbers are scarce and self-reported, so treat all of these as unverified. The most-cited figure of the year is an X post claiming 2,700 reviews on 16,000 downloads in two weeks, a 17 percent review rate, by prompting a prayer app right after the user's first prayer, first streak or roughly ten minutes of use ¹⁴. The Android developer with a million monthly users was seeing about 70 reviews a day before the dialog stopped, with the prompt shown 1.2 times per user per month, which works out to a fraction of a percent of users per day but a healthy absolute number ¹⁰. Bartlett's funnel assumes half of users reach the wow moment and roughly a third of those leave a rating, which yields a 4.8 average once the inevitable one-stars from bugs are included ¹³. The IndieDev thread's number is smaller and more honest: 10 to 15 ratings from people you know, then a slog to 50 ¹².

How this shows up in the charts

Ratings count and rating velocity are inputs to both stores' ranking and featuring, so a working prompt changes chart position in two ways that AppWinners' daily snapshots make visible. First, an app that crosses a few hundred ratings with a 4.7 or better converts a higher share of product-page visitors, which lifts it within its category over a few weeks without any change in marketing ¹⁵. Second, a prompt that silently breaks, as the Play dialog did for one large app in April 2026, shows up as flat or sinking rank with no corresponding change in downloads, a signature worth checking before you blame the algorithm ¹⁰. On iOS, Apple's editorial team is reported to prefer apps that already have a substantial body of reviews, so the difference between a dozen reviews and a few thousand is also the difference between being eligible for a feature and not ¹⁵.