What is app uninstalls?
Table of Content:
How uninstalls are detected (without the fluff)
On Android: Firebase logs an app_remove event when the package is deleted; many platforms consume that signal for uninstall tracking.
On iOS: there’s no direct “uninstall” event; vendors infer it by sending silent pushes and marking tokens that come back invalid (APNs). Expect batch updates with some delay.
In app store dashboards: Google Play Console reports uninstall events to help you correlate loss with crashes/ANRs and app size.
Why it matters
- Uninstalls are common — and expensive. AppsFlyer’s 2025 benchmarks highlight persistent uninstall pressure across categories (fresh 30-day views by vertical).
- Recent averages are still high. Adjust reports a 45% global uninstall rate in 2024 (share of installs that later removed the app).
- Many happen fast. For gaming on Android, ~43% of uninstalls occur day 0/1 after install.
KPIs & formulas you’ll actually use
- Uninstall Rate = Uninstalls ÷ Installs × 100. Track by cohort (install date) and time window (D1, D7, D30).
- Time to Uninstall (TTU): median hours/days from install to remove (great for spotting onboarding issues).
- Reinstall Rate: % of uninstalled users who return in 30/90 days.
- Churn vs. uninstall: churn = inactive; uninstall = deleted. Monitor both.
Fast diagnostic flow
- Spike check: Did uninstalls jump after a release, pricing change, or ad burst?
- Quality: Correlate with crashes/ANRs in the same period. Fix first.
- Size & performance: App size increases and slow cold starts drive removals; review Play Console size metrics.
- Lifecycle pressure: Audit notification volume, cadence, and relevance.
- Monetization pressure: Frequency and intrusiveness of ads (especially interstitials) are uninstall triggers.
- Acquisition mix: If day-0/1 uninstalls are high, your ad promises don’t match first-run experience.
How to reduce uninstalls
- Nail first run: cut steps in onboarding, prefetch content, show immediate “aha.”
- Fix stability before growth: ship crash/ANR budgets per release; guardrails in CI.
- Right-size the app: use app bundles, on-demand modules, and asset packs.
- Tame notifications: cap frequency, batch low-value pings, personalize triggers.
- Respect ad UX: prefer rewarded/opt-in; keep interstitials at natural breaks.
- Close the loop: survey exit reasons, run holdout tests, and watch cohort LTV — not just D1.
FAQs
What are app uninstalls?
Uninstall definition is when users delete your app from their device — an explicit churn signal you can measure and trend.
Can I track iOS uninstalls?
Directly, no. Indirectly, yes — via silent push token invalidation through APNs (batched/lagged).
Why do uninstall numbers differ across tools?
Different methods (APNs/FCM feedback, sampling windows, dedupe rules) and platform limits lead to variance. Use one source of truth for trending.
What’s a “good” uninstall rate?
It’s vertical- and cohort-specific. Use category benchmarks (e.g., AppsFlyer/Adjust) as a sanity check, then set targets per channel and release.
Can ad campaigns cause uninstall spikes?
Yes — mismatched creative promises, intrusive ad formats, or low-fit users can drive day-0/1 removals. Watch TTU and post-install behavior.