Help for owners
People download my app and then stop using it
Short answer
First measure where people stop. Retention is the share of people who open the app again after the day they installed it, and Apple shows it in App Store Connect Analytics. Then look at crashes and reviews for the same period. Without screen-level analytics the cause stays a guess, so a developer has to add event tracking.
Does this sound like your situation?
- Downloads look healthy but few people seem to come back.
- New users sign up and never do the main thing the app is for.
- Reviews say the app is confusing, slow or broken, but nobody agrees on which.
- I cannot tell if a drop started after a particular update.
- My developer and my marketing agency each give a different reason.
Why does this happen?
Retention is measured by day, not by feeling
Apple defines retention as the share of devices that open the app in the days after a download. Day 7 retention, for example, is the share of the original group still active seven days later. Apple also offers peer group benchmarks to compare crash rate and retention against similar apps.
Confirmed by developer.apple.com
Crashes and freezes make people leave quietly
Google Play's Android vitals reports the percentage of daily users who had at least one crash or not-responding error. A person who meets one early may simply never open the app again.
Confirmed by support.google.com
The store data stops at the front door
Apple's usage data only includes users who agreed to share diagnostics and usage information. Neither store tells you which screen in your own app people abandoned. That needs events defined inside the app.
Confirmed by developer.apple.com
Events show the path through the app
With Google Analytics for Firebase you can define custom events for the steps that matter to your business and build audience groups from them. That turns 'people leave' into 'people leave after step three'.
Confirmed by firebase.google.com
What can I do about it today?
- Read the retention numbers you already haveIn App Store Connect, open the app, then Analytics. Look at the retention cohorts by download date. In Google Play Console, look at the user statistics. Reading changes nothing.
- Mark the dates of your updatesWrite down when each version was released. Check whether a drop in retention or rating starts at one of those dates.
- Read the last 30 one-star and two-star reviewsSort them into groups, such as crashes, login, speed, price and confusing screens. The biggest group is your first lead.
- Try the first five minutes yourselfDelete the app from a spare phone, install it fresh and sign up as a new user. Write down every moment you hesitate. Use a test account, not a customer's.
- Ask five users directlyEmail or call people who stopped using it and ask one open question: what did you expect to happen? Do not promise anything in return.
When should I bring someone in?
- You cannot find a pattern in the reviews or the store numbers.
- You are spending on ads to replace users who leave.
- The app has no event tracking, so nobody can see where the path breaks.
How do I handle it?
- Define the key pathWith you I write the three or four steps a new user must complete for the app to be useful to them.
- Add tracking for those stepsI add events to the app so every step is counted, and I check that crash reporting is in place as well.
- Read the data against the reviewsAfter enough users have gone through the new version, I compare where they stop with what the reviews say.
- Fix the largest leak firstI propose one or two changes in writing, with the reason for each, and you decide. I do not redesign everything at once.
- Measure againThe next release is compared against the previous one, so you can see if the change helped.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
What is a good retention rate?
It depends on the kind of app. Apple's peer group benchmarks let you compare your crash rate and retention with similar apps, so that is a better yardstick than a single number.
Is it the design or a technical problem?
Often both, and the data separates them. Crashes and not-responding rates point to technical causes. A steady drop at one screen points to design or wording.
Can you promise users will stay?
No. People's choices belong to them. I can show you where they stop and fix what is in the way.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.