One star: "crashes every time I open it"
You paid for an app. It launched, and for a while it was fine. Now the store page is full of one-star reviews. It crashes on login. It freezes on the payment screen. It logs people out. It drains the battery. Customers email support, support forwards it to whoever built the app, and the reply is that it works fine on their phone.
Downloads are dropping, the rating is sinking and you are starting to wonder if the whole thing needs throwing away.
Why apps end up like this
Apps rarely start broken. They drift. New phone models and operating system versions arrive every year, and an app that is not updated for them starts to fail in ways it never did at launch. Third-party libraries go out of date. The back end changes and the app does not.
More often than not, there is also no visibility. Without crash reporting, the only evidence is reviews and emails, which say "it crashed" but not where, on which phone or why. Fixes are guesses, and guesses break other things.
And there is often no testing routine. Each release goes out after a quick try on the developer's own phone, so issues on older Android devices or small iPhones reach users first.
What a failing app costs
| Symptom | Business effect |
|---|---|
| Low store rating | Fewer new downloads, because people read the reviews |
| Crashes at checkout or booking | Lost sales at the most valuable moment |
| Uninstalls | Customers lost, often to a competitor's app |
| Support load | Staff time answering complaints about the same faults |
| Brand damage | The app becomes the thing people say about you |
Reviews stay visible long after the fault is fixed, which is why acting sooner matters. Each week of crashes adds to a record new users will read.
The relationship with the original developer often suffers too. You are told it works on their phone, they are told it is broken, and neither side has evidence. Money goes on fixes that do not fix anything, and trust drains away on both sides until someone suggests starting again from scratch, which is rarely the cheapest or safest option.
How we fix it
- Instrument first. We add crash and error reporting, such as Firebase Crashlytics or Sentry, and basic performance monitoring, and release that as a small update. Within a short time we have real data instead of guesses.
- Read the reviews properly. We group store reviews and support emails by complaint, and match them to the crash data, so we know which problems users feel most.
- Code review. We review the code, dependencies and build setup, and give you a plain assessment: fixable, fixable with some areas rebuilt, or unsound.
- Fix the top causes. Crashes usually cluster. We fix the issues behind most of them first, often out-of-date libraries, unhandled network errors, memory problems and login token handling.
- Test on real devices. Each release is tested across a spread of real and cloud-hosted devices, old and new, before it reaches users. Staged rollouts release to a small share of users first.
- Respond in the store. We help you reply to reviews when a fix ships, which shows current users something has changed.
- Crash reporting usually gives a much clearer picture of what is going wrong
- A rebuild is recommended only if the review shows the foundations cannot be fixed
- You receive the code, build setup and store access, whatever we recommend
What changes afterwards
Releases go out with evidence behind them. You can see crash rates, which versions are affected and whether the last fix worked. Support stops receiving the same complaint every day, and new reviews start to reflect the app as it is now rather than as it was.
Most importantly, there is a routine: dependencies kept up to date, testing before each release, and monitoring that spots a new problem before the reviews do.
Does this sound like your app?
- Your app store rating has dropped because of crash complaints
- The developer cannot reproduce the problems users report
- There is no crash reporting in the app
- The app has not been updated for recent phone or operating system versions
- You are being told the only answer is a full rebuild