Most sudden rating drops have the same story: an update ships, something breaks for a group of users, and the one-star reviews arrive before the team notices. This checklist helps you catch problems early — on iOS and Android.
Before the release
- Beta test the build. Use TestFlight and Google Play testing tracks — see beta testing. Include older devices and OS versions.
- Check the riskiest flows by hand: sign-up, login, purchase, restore purchases, data migration.
- Write clear release notes. Users who know what changed complain less about changes.
- Prepare reply templates for likely problems (login issues, moved features) — see how to respond to app store reviews.
- Decide who's on watch for the first 48 hours.
Choose a gradual rollout
- App Store: enable phased release — the update goes to automatic-update users over 7 days (1%, 2%, 5%, 10%, 20%, 50%, 100%), and you can pause it.
- Google Play: use a staged rollout — start at 5–10% and increase when the numbers look good. You can halt it.
A gradual rollout turns a disaster into a small incident.
Release day: what to watch
- Crash rate in Crashlytics, Xcode Organizer or Android vitals — compare with the previous version. See crash rate.
- New reviews. Users report problems in app reviews within hours — often with details your crash tool doesn't have ("since the update I can't log in with Google"). Have them arrive in Slack or Teams with app review monitoring.
- Support inbox — a spike in tickets is an early signal too.
- Key metrics: sign-ups, purchases, logins.
Rule of thumb: three reviews describing the same new problem = pause the rollout and investigate.
When something breaks
- Pause or halt the rollout (App Store Connect: pause phased release; Play Console: halt staged rollout).
- Confirm the issue and its scope (devices, OS versions, countries).
- Reply to affected reviews with a short, honest developer response: you know about it, a fix is coming.
- Ship a fix — consider requesting an expedited review from Apple for critical bugs.
- Update your replies when the fix is live; reviewers get notified and often update their rating.
The week after
- Compare the average rating of the new version with the previous one.
- Tag the new reviews: what do people like, what confuses them?
- If the new version fixed problems behind a low rating, consider whether an iOS rating reset makes sense next time.
- Turn your learnings into the next release's checklist.
Make review watching automatic
The difference between a small incident and a ratings disaster is usually hours. allstarsbot sends every new App Store and Google Play review to Slack or Microsoft Teams, so the whole team sees release problems the moment users report them. Free for 7 days.
