Google sets limits for crashes and freezes
Google Play's "bad behavior" limit is 1.09% of users seeing a crash and 0.47% seeing a freeze, overall, or 8% on any one phone model.
Source: Android Developers (Creative Commons Attribution 2.5)
Bad reviews, crashes and complaints
Start with the crash and freeze numbers Apple and Google already collect, not with the reviews, then fix what hurts the most customers before adding anything new. This is for established businesses whose customers or staff depend on the app. We start with an $8,000 audit that takes 1 to 4 weeks: you learn what is driving the complaints, what to fix first, and get a fixed quote for the work.
For businesses whose customers or staff depend on the app.Audits are $8,000, in 1 to 4 weeks.
What Apple and Google say
Each fact links to the platform that set the rule. Both stores track more than stars, and both publish what they do about it.
Google Play's "bad behavior" limit is 1.09% of users seeing a crash and 0.47% seeing a freeze, overall, or 8% on any one phone model.
Source: Android Developers (Creative Commons Attribution 2.5)
If an app goes over a limit, Google Play may show it to fewer people and may put a warning on its store listing.
Source: Android Developers (Creative Commons Attribution 2.5)
Quality is judged on the last 28 days of data. Emerging problems are flagged early enough to leave 21 days to fix them. Google's advice is to fix the crashes and freezes affecting the most users first.
Source: Android Developers (Creative Commons Attribution 2.5)
On the App Store you can reply publicly to a review. The customer is told you replied and can update their review. Replies must not contain marketing.
Source: Apple Developer
When you release a new version you can reset the app's overall rating. It cannot be undone, it applies in every country at once, and written reviews stay up.
Source: Apple Developer
Apps must use Apple's own review prompt, which a person sees at most three times in a year. Home-made review prompts are not allowed. Apps that crash on launch are removed from the App Store straight away.
Source: Apple Developer
Look at the crash and freeze numbers before you read the reviews.
Google Play Console shows them for the last 28 days. The limits are 1.09% of users seeing a crash and 0.47% seeing a freeze, or 8% on any one phone model.
If you are over a limit, treat it as urgent.
Google may show the app to fewer people and put a warning on your listing.
Pause new features until the top problems are fixed.
The complaints are usually about features you already have, not ones you are missing.
Fix the problems that hit the most people first.
Google gives the same advice. A long list fixed at random rarely moves the rating.
Reply to recent bad reviews, briefly and without selling.
On the App Store the customer is told you replied and can update the review.
Ship the fix, then decide whether to reset the Apple rating with that release.
A reset cannot be undone and applies in every country, and old written reviews stay visible.
Ask happy customers for a rating at a good moment, using Apple's own prompt.
Each person sees it at most three times a year, so choose the moment carefully.
Check that the app opens on every device you support.
An app that crashes on launch can be removed from the App Store straight away.
What it costs
For one app and one codebase, in 1 to 4 weeks. Larger apps are quoted higher. The audit is paid on its own; the fixes it recommends are quoted separately, and maintenance after that starts at $10,000 a month with a three-month minimum. Prices are for remote work. On-site work is quoted separately and priced higher.
How the audit worksThe crashes, freezes, slow screens and broken flows behind the complaints, ranked by how many people they affect.
A short, ordered list, starting with what hurts the most customers.
Features or changes to pause until the app is stable.
For the fixes, or for maintenance that keeps the ratings from sliding back, if you decide to go ahead.
Case study
Therapists relied on the app every day, and the team wanted to keep adding features. We showed them the existing features were the problem and fixed those first. In controlled before-and-after testing on a current iPad, our testing observed the time to open an important record drop from approximately 10 seconds to under one second.
Read the case studySomething usually did change: a new phone or operating system version, a backend change, or an update that broke one path. The crash and freeze numbers in App Store Connect and Google Play Console usually show where to look.
Not because they are negative. On the App Store you can reply, and the customer can update the review. Once a fix ships you can also reset the overall rating, but the written reviews stay.
Often, yes. Most of that work is usually worth keeping. We start with the audit: we read the code, check who holds the store accounts and signing keys, and tell you what can ship as it is and what has to be fixed first. Then you get a fixed quote. We don't promise a date before reading the code.
Not by default. Most apps that customers complain about can be fixed. The audit tells you what to keep, fix or replace, and what each costs.
1 to 4 weeks, and $8,000 for one app and one codebase. Larger apps are quoted higher.
A short note is enough. We reply with whether we can help and what the first step costs.