You're asking for ratings at the worst possible time.

Your star rating is the first thing a store visitor sees — it renders in search results, next to your icon, before anyone opens the listing. Yet the prompt that builds it is the most carelessly fired dialog in most apps: triggered by a launch counter, at a moment chosen by arithmetic instead of the user's mood. Here's how the prompt actually works on both stores, and when to spend it.

The prompt is rationed — spend it like it

On iOS, the system rating prompt (the requestReview API) will show at most three times per year for your app on a given device. And your call is a request, not a command: the system can silently decide not to show anything, users can switch prompts off globally in Settings, and Apple deliberately gives you no callback telling you whether the dialog appeared. You get three real chances a year, and you can't even count them.

Google Play's in-app review API works the same way with less transparency: the flow is quota-limited so users don't get spammed, but Google doesn't publish the numbers — and the API is designed so your app can't tell whether the dialog was shown, dismissed, or completed. Google's own guidance draws the logical conclusion: don't wire the API to a "Rate us" button, because quota may turn the tap into a silent nothing.

Now look at the most common implementation in the wild: prompt on the third launch. That spends a rationed, unobservable, once-a-quarter resource at a moment selected by a counter — which might be mid-task, mid-frustration, or thirty seconds after a crash. It's the marketing equivalent of proposing on a stopwatch.

Ask at the moment of earned value

There is exactly one good time to ask: right after the user got what they came for. The workout is logged. The invoice sent. The level cleared. The export finished. Ratings are a mood measurement, and the mood you want on record is "this thing just worked for me."

So the trigger shouldn't be a timer — it should be your app's win moment. Every app has one; if you can't name yours, that's a product question worth answering before a ratings question. Then gate it so the prompt only fires when goodwill has actually accumulated:

A sane gate: the user has hit the win moment several times, the install is at least a week old, and you haven't asked recently. Track this yourself even though the OS enforces its own limits — the OS quota controls how often you may ask; only your gate controls when. Never ask in the first session (no goodwill yet), never interrupt a task in progress, and never on any path that follows an error, a failed sync, or a payment problem.

What the stores actually ban

The folklore workaround — ask "Enjoying the app?" first, send happy users to the store and grumpy ones to a feedback form — has aged badly. Google Play's guidelines for the in-app review flow are explicit: don't ask the user any qualifying questions before or while showing the prompt, and don't attach incentives. The pre-filter pattern is, on Play, simply against the rules.

Apple's App Store Review Guidelines, for their part, require you to use the provided system API when asking for ratings inside the app and disallow custom review prompts — that's why every compliant iOS app shows the identical sheet. Incentivized reviews ("rate 5 stars for 100 coins") are banned on both stores and are a classic removal-and-purge trigger. The compliant version of the old funnel is to make feedback channels permanently easy to find — a "Something broken?" row in settings, a contact link on error screens — so frustrated users always have a lower-friction outlet than the review box.

The settings-row escape hatch

The quota only applies to the in-app prompt. A user who wants to leave a review should never have to wait for one — give them a "Leave a review" row in settings that deep links straight to the store. On iOS, append ?action=write-review to your App Store URL and the review sheet opens pre-armed; on Android, link to your Play listing. This costs nothing against any limit and catches your happiest users at their own chosen moment.

And answer your reviews. Developer replies are public on both stores, and reviewers can update their rating after you respond — a fixed bug plus a two-line reply is one of the few honest ways to turn a two-star into a four.

Why the stars deserve this much care

Because they compound. The rating shows in search before the listing is ever opened, feeds both stores' ranking systems, and frames how every screenshot after it is read — 4.8 stars says "the screenshots are telling the truth." Two mechanics work in your favor: Google Play's displayed score weights recent reviews more heavily than old ones, and both stores compute ratings per country. A rough launch isn't a life sentence; recent quality wins. Apple even lets you reset your summary rating when you release a new version — a nuclear option that also wipes your social proof, worth it only after a genuinely disastrous release.

Stars are half the search card. Fix the other half.

When your listing appears in search, a visitor sees exactly two things: the rating you earn in-app, and the icon-plus-screenshots you control completely. If you're putting this much thought into the prompt, spend an hour on the frames next to it — ShotCanvas turns raw screens into a polished, consistent set for every App Store and Google Play size, free to start.