- Most uninstalls trace back to a few fixable causes: slow or heavy apps on low-end Android phones, crashes, too many notifications, and outdated builds.
- Watch crashes and ANRs in Firebase Crashlytics and Play Console Android vitals before you spend on re-engagement.
- Track day-1, day-7 and day-30 retention cohorts for each release, so you can see whether a change helped.
- Use the official in-app review APIs at the right moment, and read and reply to store reviews. A monthly checklist is below.
The app is live and downloads are coming in. A few weeks later, installs keep rising but daily users do not. People open the app once, perhaps twice, and then it disappears from their phone. Marketing more will not fix this; you are filling a bucket with a hole in it.
This post is about what happens after launch. First-run experience, OTP login and permission prompts are covered in planning an app: MVP scope, UX and store optimization, so we only touch them briefly here. The rest is about performance, stability, notifications, reviews and measurement.
Start with the causes you can measure
Users rarely tell you why they left. You infer it from data and from reviews. Below are the usual causes, how to check each, and what to do.
| Likely cause | How to check | Typical fix |
|---|---|---|
| Slow start or heavy app | Test on a cheap Android phone; check app size and startup time in your tools | Compress images, remove unused libraries, lazy-load screens |
| Crashes and freezes | Crashlytics, Android vitals (crash rate, ANR rate) | Fix the top crash first; ship a patch |
| Too many notifications | Notification opt-outs, OS-level disables, uninstalls after sends | Cut frequency; segment by behavior |
| Broken after an OS update | Crashes clustered on a new OS version | Test on beta OS builds; update SDKs |
| No clear value after first use | Day-1 and day-7 retention; funnel drop-offs | Rework the first-session journey |
Size and speed on low-end Android phones
A large share of Indian users are on budget Android devices with limited storage and memory. If your app is large, it is one of the first things to go when the phone says “storage full”. If it takes many seconds to open, people stop opening it.
- Test on a real low-priced phone, on a 4G or weaker connection, not only on your own device.
- Check the install size and remove unused packages and assets. Serve images in modern compressed formats and the sizes actually needed.
- Keep the first screen light. Load heavy content after the user sees something useful.
- Cache what you can so the app works acceptably when the connection drops.
Cross-platform apps are not automatically slower or heavier, but they need the same attention. Our Flutter app maintenance and support covers profiling and size reduction for those builds.
Monitor crashes and ANRs
An app that crashes loses users quietly. On Android, an ANR (“application not responding”) happens when the app is frozen for too long. Two established tools give you data:
- Firebase Crashlytics groups crashes by cause and shows how many users each one affects, on both Android and iOS.
- Play Console Android vitals reports crash and ANR rates for your published app, which Google also uses as part of how it assesses app quality on Play.
Review them weekly after launch. Fix the crash that affects the most users first, not the one that is easiest. After each release, compare crash-free users to the previous version. For iOS, Xcode Organizer and App Store Connect provide crash reports as well.
Push notifications: fewer, more relevant
Notifications can bring users back, and can also push them to turn alerts off or uninstall. Ask of every message: does it help this user right now?
- Send transactional messages (order shipped, payment received, appointment reminder) always; they are expected.
- Limit promotional messages and segment them. A user who never bought electronics does not need an electronics sale.
- Avoid sending at night. Respect time zones if you serve customers abroad.
- Watch for warning signs: rising notification opt-outs, users disabling notifications in system settings, and uninstalls soon after a campaign.
On iOS, and on Android 13 and later, the user has to grant permission before you can send any notification. Track what share of new users grant it; if that share falls after a release, check whether the permission prompt moved to a worse moment. If many of your customers never allow notifications, order updates on WhatsApp may reach them better, which we cover under WhatsApp marketing.
Keep up with OS and SDK requirements
Apple and Google release a major OS version every year and raise their build requirements on a regular cycle. Google Play requires new apps and app updates to target a recent Android API level, and an existing app that falls too far behind stops being offered to new users on newer Android versions, even though current users keep it. Apple periodically requires App Store submissions to be built with a recent Xcode and SDK. An app nobody touches can therefore start misbehaving on new phones, vanish for new users, or block your next urgent fix until the project is upgraded.
The exact levels and dates change every year, so check the Android developer documentation, Play Console policy notices and the Apple developer site rather than relying on a date you read once. Plan one upgrade cycle a year: install the developer betas when they appear (Apple’s usually follow its June developer conference; Android publishes its own schedule), update dependencies, and release before the stable OS reaches most of your users. This is a core part of app maintenance and support.
Release in stages so one bad build cannot sink you
A release that crashes on launch can undo months of retention work in a weekend. Both stores let you limit the damage:
- Google Play staged rollouts: release the update to a small percentage of users first, watch Crashlytics and Android vitals for a day or two, then increase the percentage. You can halt a rollout if crashes climb.
- App Store phased release: automatic updates go out gradually over seven days, and you can pause the release if something breaks. Users can still update manually.
A simple rule: do not move past the first stage until the crash-free rate of the new version matches or beats the previous one.
Ask for reviews the right way
Both stores provide official in-app review prompts: the Play In-App Review API on Android, and StoreKit’s review request on iOS (AppStore.requestReview in current SDKs, which replaces the older SKStoreReviewController call). They show a native rating sheet without sending users out of your app. Both are rationed: Apple shows the prompt at most three times per user in a 365-day period, and Google Play applies its own time-based quota that it does not publish. In both cases the system decides whether the sheet appears, so you cannot force it.
- Ask after a success moment: an order delivered, a task finished, a goal reached. Never on launch or after an error.
- Do not trigger the prompt from a “Rate us” button. If the quota is used up, nothing happens and the button looks broken. For a permanent button, link to your store listing instead.
- Do not ask “Do you like the app?” or “Would you give us 5 stars?” before showing the prompt; Google’s in-app review guidelines forbid it. Never offer a reward for a rating on either store.
- Keep a “Send feedback” option in the help or settings screen for everyone, so complaints reach you directly instead of only appearing in public reviews.
Read and reply to store reviews
Store reviews and support messages are free research. Each week, read new reviews and tag them: crash, slow, login, price, missing feature. Patterns show what to fix. Reply to complaints with specifics, such as “this was fixed in version 2.3; please update”, and invite the user to write to support. Replies are visible to future users and sometimes lead the reviewer to update their rating.
Measure retention with cohorts
A cohort is a group of users who installed in the same week or on the same release. For each cohort, track how many were active on day 1, day 7 and day 30. Compare cohorts over time: if the day-7 figure improves after a release, you have evidence the change helped. Avoid chasing outside benchmarks, since they vary widely by category; compare your app with its own history. Add event tracking for the actions that show value (first order, first booking, first saved item) and see which of them correlate with users who stay.
Monthly post-launch checklist
- Review crash-free users and ANR rate for the current version; fix the top issue.
- Test the latest release on one low-end Android phone and one older iPhone.
- Check app size against last month.
- Update libraries and SDKs; note any store deadline in the next quarter.
- Review notification sends against opt-outs and uninstalls.
- Read all new store reviews, tag them and reply.
- Compare day-1, day-7 and day-30 retention for the latest cohorts.
- Decide the one change for next month based on the data.
Android and iOS builds have their own tooling and store rules; see Android app maintenance and iOS app maintenance for what each covers.
Frequently asked questions
Why do users uninstall apps?
Common reasons are crashes, slowness, storage space, too many notifications, and not seeing enough value after the first sessions. Check your crash data and low-end device performance first, then review notification frequency and the first-session experience. Read recent one-star reviews too: they often name the cause directly.
What is a good retention rate for an app?
It varies by category and audience, so a single number is misleading. Measure your own day-1, day-7 and day-30 retention by cohort and aim to improve against your previous releases rather than an outside benchmark. A rising day-7 figure after a release is the clearest sign a change worked.
How often should I send push notifications?
There is no fixed number. Send transactional messages when needed and keep promotional ones limited and relevant. If opt-outs or uninstalls rise after campaigns, you are sending too many or sending to the wrong segment. Cut the lowest-performing campaign first and compare the next month.
How do I get more app store reviews?
Use the official in-app review prompts after a positive moment, such as a completed order. Do not reward reviews or filter who is asked. Reply to existing reviews, since visible responses show users that you act on feedback. Never trigger the prompt from a button; link to the store instead.
Losing users after launch?
We can review your crash data, performance on low-end phones and release process, and set up monthly maintenance for your app.
See app maintenance support →