Review policy and rating crises

Expert: with sources and numbers. Plain: the same, without them, for beginners.

What both platforms prohibit around ratings, where the line falls and what to do when a rating collapses for outside reasons.

Verified 2026-09-19 · 38 days ago both ratings policy process

40-08 covers the mechanics: prompt APIs, responses, the rating reset. This page covers the two things that get people into trouble: what is prohibited, and what to do when the rating drops for reasons that have nothing to do with the app.

What Apple prohibits

A Apple’s opening statement, verbatim: “If you attempt to cheat the system (for example, by trying to trick the review process, steal user data, copy another developer’s work, manipulate ratings or App Store discovery) your apps will be removed from the store and you will be expelled from the Apple Developer Program.” (App Review Guidelines, verified 2026-09-19)

A And specifically: “If we find that you have attempted to manipulate reviews, inflate your chart rankings with paid, incentivized, filtered, or fake feedback, or engage with third-party services to do so on your behalf, we will take steps to preserve the integrity of the App Store, which may include expelling you from the Apple Developer Program.” Same source.

A Guideline 5.6.3, Discovery Fraud: “Manipulating any element of the App Store customer experience such as charts, search, reviews, or referrals to your app erodes customer trust and is not permitted.” Same source.

A Guideline 3.2.2(vi): apps must not require users to rate or review the app (or watch videos, download other apps, tap advertisements or enable tracking) in order to access functionality or content, or to receive monetary or other compensation, including gift cards and codes. Same source.

Read 3.2.2(vi) carefully: the prohibition is on conditioning access or reward on the rating. That is the bright line.

Note also the word “filtered” in the manipulation clause. It appears alongside paid and fake, and that has a direct consequence. See gating, below.

What Google prohibits

A “Developers must not attempt to manipulate the placement of any apps on Google Play. This includes, but is not limited to, inflating product ratings, reviews, or install counts by illegitimate means.” (Ratings, Reviews, and Installs policy, verified 2026-09-19)

A The same policy prohibits offering rewards in exchange for positive feedback, such as a discount tied to a high rating, paid or automated fake installs, and fake reviews posing as users, including reviews containing affiliate links, coupons or promotional material for other apps. Same source.

Where the line actually falls

Allowed: asking every user to rate, at a moment of your choosing. Asking in the app description. Responding to reviews. Fixing the thing people complain about and asking again after.

Prohibited: paying for reviews. Incentivising a rating with anything of value. Conditioning features or rewards on rating. Using a service that generates reviews. Filtering who gets asked based on how they will answer.

The gating question. “Gating” means asking users how they feel first, then routing only the happy ones to the store prompt and the unhappy ones to a support form.

C It is widely practised and widely described in practitioner material, including the Advanced ASO e-Book reviewed here, which flags it as controversial.

It is not explicitly named in either policy. But Apple’s manipulation clause lists “filtered” feedback alongside paid and fake, and gating is filtering by definition. This base does not recommend it. If your organisation does it, that should be a decision someone made deliberately with the clause in front of them, not a pattern that arrived with a third-party SDK.

A defensible alternative that achieves most of the same thing: pick the trigger better. A Apple’s own guidance is to request when users are likely to feel satisfied, after completing an action, level or task (Ratings and reviews, verified 2026-09-19). Prompting after a success is selecting a moment, not filtering a person.

When the rating collapses and the app did not change

Rating drops that have nothing to do with a release: an outage during a high-traffic moment, a controversial product decision, a pricing change, a real-world event that makes people angry at you, or coordinated review activity.

A live sports app is unusually exposed, a failure during a major match produces a concentrated burst of one-star reviews from people who are all upset about the same twenty minutes.

What to do, in order:

1. Establish whether it is real. Volume, timing, and whether the reviews describe a genuine problem. A burst of one-stars describing a real outage is feedback, not an attack.

2. Fix the thing, if there is a thing. Everything below is worthless if the cause is still live.

3. Respond to the current-version reviews. A Apple notifies the reviewer when you respond, and the reviewer can then update their review (Ratings and reviews, verified 2026-09-19). This is the only documented mechanism that turns an existing bad rating into a better one. Prioritise recent, low-star, current-version reviews.

4. Report reviews that are actually abusive or fraudulent to Apple or Google, rather than responding to them. Reporting is the sanctioned route; retaliating in a public response is not.

5. Do not reach for the rating reset first. A It resets the summary rating but not the written reviews, and Apple advises using it sparingly because few ratings may discourage downloads (Ratings and reviews). After a genuine relaunch that fixed the complaint, it is reasonable. As a way to escape a bad month, you lose the volume that made the rating credible and keep the text that explains why it was low.

6. Remember ratings are per-territory on iOS. A Same source. A crisis in one market does not follow you into another, and a market-specific problem shows up as a market-specific rating, which is also a diagnostic.

7. Write down what happened. Date, cause, depth, recovery time. The second time this happens, the useful thing is knowing how long the first one took to recover.

What goes wrong

Buying reviews. Expulsion from the Developer Program is the stated consequence, not a warning.

Incentivising a rating. Prohibited on both platforms, explicitly.

Gating because a tool made it easy. “Filtered” is named in Apple’s clause. Decide it deliberately or not at all.

Responding angrily to a review bomb. Public, permanent, and covered by the Developer Code of Conduct, which asks you to treat everyone with respect in responses to App Store reviews.

Resetting the rating to escape a bad month. Keeps the reviews, loses the volume.

Not responding to the reviews that can still change. The current-version one-stars are the only ones a response can move.

In short

Every fact on this page in one line, with its evidence tier, source and verification date, 5 A. Generated from the claim register, so it cannot drift from the page above.

A Guideline 3.2.2(vi): apps should not require users to rate the app, review the app, watch videos, download other apps, tap on advertisements, enable tracking or take similar actions in order to access functionality or content, use the app, or receive monetary or other compensation including gift cards and codes.
IOS-POL-010 · verified 2026-09-19
A Apple states that attempting to manipulate reviews, inflate chart rankings with paid, incentivized, filtered or fake feedback, or engaging third-party services to do so, may result in expulsion from the Apple Developer Program. Guideline 5.6.3 Discovery Fraud states that manipulating any element of the App Store customer experience such as charts, search, reviews or referrals is not permitted.
IOS-POL-011 · verified 2026-09-19
A Users with Admin or Customer Support roles can respond to all App Store reviews regardless of age, edit responses at any time with only the latest displayed, and notify the reviewer, who can then update their review.
IOS-RATE-003 · verified 2026-09-19
A Each App Store territory has its own summary rating, which can be reset when submitting a new app version. Apple advises using this sparingly because few ratings may discourage downloads. Resetting the summary rating does not reset written reviews.
IOS-RATE-004 · verified 2026-09-18
A Google Play prohibits attempting to manipulate app placement, including inflating product ratings, reviews or install counts by illegitimate means; offering rewards in exchange for positive feedback such as discounts tied to high ratings; paid or automated fake installs; and fake reviews posing as users, including reviews containing affiliate links, coupons or promotional material for other apps.
PLAY-POL-006 · verified 2026-09-19

Think your app deserves better?

Send the App Store link.
The audit comes back within two working days, whether you hire us or not.

Free, and we mean it. No card, no call required.