What triggers it
- A controversial change: a price increase, a removed feature, a new subscription.
- News or social media outrage about the company.
- Organized campaigns, sometimes by fans of a competitor.
A review bomb looks different from a bad release: the reviews arrive within hours, repeat the same complaint, and often have nothing to do with how the app works.
How to respond
- Notice it early. App review monitoring in Slack or Teams shows a spike in real time instead of in next week's report.
- Report abuse to the store. Apple and Google remove reviews that break their guidelines (spam, off-topic, hateful content). Both have systems that detect unusual review activity.
- Reply calmly with a developer response to representative reviews — explain the change or what you're doing about it.
- Fix the real cause if there is one. Many bombs are about a legitimate complaint.
Example
A popular game adds an energy system. Within a day, 2,000 one-star reviews say "pay to win". The team pins an explanation, adjusts the system a week later, and replies to the top reviews — the rating recovers over the following month.