Fake Reviews and Review Bombing: Report and Recover

A cluster of one-star ratings landing overnight is one of the few events that can move a small app's rating by a full star in a day, and developer forums in the past year are full of people watching it happen. The good news is that both stores have a reporting path and a few blunt tools for recovery; the bad news is that what they will and will not remove is narrower than most developers hope.

What developers are asking

Three questions come up again and again. The first is "a competitor is leaving one-star reviews, can I do anything?" A December 2025 r/iOSProgramming thread describes two one-star ratings arriving the night after a rival's marketing account viewed the developer's TikTok page; the top answer, with 34 upvotes, was to reply professionally and ask what went wrong, and a second commenter suggested documenting the timing in case a report to Apple was needed later ¹⁰. A thread the next day described five consecutive one-star reviews, one of which called the app "vibe coded slop" and claimed constant crashes that Crashlytics did not show; the reviewer's name matched an account created only after the developer replied ¹¹.

The second is "how do I stop a single bad rating from wrecking a young app?" Early ratings are brutal arithmetic: one developer reported seven five-star reviews dragged to a 4.0 average by two one-stars, and the consensus was that the pain fades after roughly 20 to 30 ratings ¹⁰. The third is "will the store remove it?" Here the answers split sharply by store, and by luck.

What Apple and Google actually remove

Apple's own guidance is to use Report a Concern, in App Store Connect under Ratings and Reviews, for reviews that are offensive, spam, or violate its terms; the reviewer is not notified ^1,2. The concern reasons are chosen from a pop-up menu and Apple does not publish a list of them, nor a response timeline ². The community's view is that Apple acts only on obvious violations such as hate speech or identical copy-pasted text, and otherwise does nothing: one developer whose niche was hit by the same reviewer leaving near-identical one-stars on several apps within days "complained to Apple and no action at all" ¹³, and the general sentiment is "Apple, not a chance" ¹⁵. Apple does say it blocked close to 195 million fraudulent ratings and reviews before they appeared in 2025, out of 1.3 billion processed, so most filtering happens upstream, invisibly ⁹.

Google is more explicit. In Play Console you open Reviews, press the flag icon on a review, and choose Report; a specialist checks it "within a few business days", removes it if it violates the Comment Posting Policy, or marks the request rejected, after which you cannot report that review again ⁴. There is also a daily cap on reports per developer account ⁴. The policy covers spam and fake reviews, reviews from multiple accounts, off-topic content, advertising, conflicts of interest, personal data, hate speech and abuse ⁶. New ratings are generally held for around 24 hours before they go public, and if Google detects suspicious activity in that window it pauses all new reviews for the app until an investigation finishes, then removes anything found abusive ⁵. Developer experience with flagging is mixed: one Android developer said flagging reviews that attack the subscription model rather than the app "has worked for me multiple times", while another replied that it "never works" ¹⁴. Several developers say they have had more luck with Google than with Apple ¹⁵.

One behaviour that nobody can report away: in some regions users read stars as a ranking, so "1 star" means "number one". Developers describe glowing text attached to one-star ratings and complaints attached to five stars; it is a cultural quirk, not fraud, and neither store corrects it ¹⁵.

What you can do while the store decides

Reply, but write for the next reader, not the reviewer. The most upvoted advice of the year (133 upvotes) was that your answer should remove the doubt a potential buyer feels when they see the one-star review ¹². Apple lets you reply to any review regardless of age; the reviewer is notified and can edit, and your response takes up to 24 hours to appear ¹. Several developers recommend waiting a few hours before replying so the tone stays calm ¹³, and one noted that a short "please contact support" line reads better than a rebuttal ¹⁰.

Add a feedback route inside the app. A developer whose hardest reviews were blank one-stars said an in-app prompt asking users to email first "cut the negative reviews significantly" ¹².

Keep evidence. Timestamps of the reviews, the competitor's visible activity, screenshots of identical wording across apps, and any email or account data that ties a reviewer to a rival all make a Report a Concern or a Play flag more credible ^10,11.

Resetting your rating

Apple lets you reset the overview rating when a new version ships: in App Store Connect, open the version, tick "Reset rating when this version is released", and submit ³. The reset applies to every storefront at once, cannot be undone after release, leaves all written reviews visible, and the product page shows a "recently reset" notice until enough new ratings arrive ³. Apple advises using it sparingly because an app with few ratings can look worse than one with a 4.3 ¹. A developer who has used it twice says nothing about it is synchronous: the app goes live unreset, flips to reset a day or two later, and new ratings appear a few days after that ¹⁶. The common advice in that thread was to reply kindly and not reset at all if you are already at 4.6 ¹⁶. Google Play has no equivalent reset; developers' only lever is that the Play listing weights recent ratings, so a run of updates and fresh positive ratings gradually buries an old wave (community reports, unverified) ¹⁴.

Protect prompt timing too. Apple's and Google's native prompts are capped and silent when the cap is hit, so the three displays a year you get on iOS should be spent after a success moment, never during onboarding, which is also where "fake-looking" negative reviews concentrate ^1,8.

The legal angle, briefly

Both stores treat buying, trading or coordinating reviews as a developer-level offence. Apple's Developer Code of Conduct says manipulating reviews or hiring a third party to do so can mean expulsion from the Developer Program ⁸, and Google's policy bans incentivised, fake or forced reviews outright ⁷. In the United States, the FTC rule that took effect in late 2024 makes it unlawful to create, buy or sell fake reviews, to pay for reviews conditional on their sentiment, or to suppress genuine ones with legal threats, with civil penalties for knowing violators ¹⁸. That cuts both ways: a competitor bombing your listing is breaking the same rule you would break by paying for five-stars. Pursuing a rival legally is rarely worth it for an indie unconfirmed, but the FTC complaint form exists if the pattern is large and provable.

How this shows up in the charts

Review bombing is usually visible in the AppWinners rank history before it is visible in the rating itself, because a sudden burst of one-stars rarely arrives without a trigger: a viral post, a price change, a policy announcement. When the PlayStation app was review-bombed in protest at Sony's decision to end physical game releases, the protest came with a spike in installs, so the app's rank climbed while its rating fell ¹⁷. For smaller apps the opposite happens: a 4.1 that drops to 3.8 after a competitor's campaign tends to show up as a slow slide down the category chart over the following two weeks, as conversion on the product page weakens ¹⁹. A reset shows up as a brief gap, the "recently reset" state, followed by whatever the new version earns.