Uninstall Survey UI: Learn Why Users Leave (iOS Reality)
A true uninstall survey is an Android idea; on iOS you catch intent earlier with an exit-intent prompt.
TL;DR
iOS gives apps no uninstall callback, so you cannot survey on delete. Instead, catch churn intent earlier with an exit-intent prompt (delete-account tap, cancellation, long-dormant return) plus an optional post-churn web survey. Build the one-question prompt from a free VP0 design and act on the top reasons.
Learning why users leave is some of the most valuable feedback you can get, because keeping a user is far cheaper than finding a new one. The honest short answer is, a true “uninstall survey” is an Android idea; iOS does not let an app run code on uninstall, so on iOS you catch intent earlier with an exit-intent or churn-risk prompt, plus an optional web survey afterward. Design that prompt from a free VP0 layout, ask one kind question, and treat the answers as a roadmap.
Why this is worth doing (and the iOS reality)
Retention economics are stark: acquiring a new user typically costs around 5x more than keeping an existing one, so understanding churn pays for itself. But be clear about the platform. On Android, apps can show a survey when uninstalled; on iOS, there is no uninstall callback, so you cannot literally survey on delete. What you can do is detect exit intent (a user heading to delete-account or settings, a long-dormant return, a cancellation) and ask then, and you can send a one-question web survey by email afterward. Apple’s account-deletion requirements mean you will often have a delete-account flow already, which is the perfect place to ask.
How to build an exit-intent prompt
VP0 is a free iOS design library for AI builders. Pick a sheet or simple form design, copy the link, and have Cursor or Claude Code build it in React Native or SwiftUI: a single question (“What is the main reason you are leaving?”) with a few tappable reasons and an optional text field. Trigger it on real signals, the delete-account tap, a subscription cancellation, or a settings visit after long inactivity, not at random. Keep it respectful and skippable; a guilt trip backfires. Send answers to analytics and tag them so you can see the top reasons over time. The delete-account flow itself must comply with Apple’s account deletion guidance.
Where and how to ask
Here are the moments and what to do at each.
| Moment | What to do |
|---|---|
| Delete-account tap | One-question reason, optional text |
| Subscription cancel | Ask, then offer a fair alternative |
| Long-dormant return | ”What kept you away?” |
| Post-churn email | Optional one-question web survey |
| Always | Respectful, skippable, no guilt |
A worked example
Say a user opens settings and taps “Delete account.” Before completing it (you still let them complete it), show a VP0-designed sheet: “Before you go, what is the main reason?” with options like “too expensive,” “missing a feature,” “found an alternative,” and “just not using it,” plus an optional text box. Log the choice, then proceed with deletion. Over a month, the tally tells you whether to fix pricing, ship a feature, or improve onboarding. Pair this with the in-app user feedback survey UI mobile for happy-path signals, a win-back push notification landing page UI to re-engage the recoverable ones, and how to get your first 100 users for an iOS app to keep the top of the funnel healthy.
Common mistakes
The most common mistake is assuming you can survey on iOS uninstall; you cannot, so catch intent earlier. The second is blocking the user from leaving until they answer, which is hostile and may violate guidelines. The third is a guilt-trip tone that sours the last impression. The fourth is collecting reasons but never tallying them, so the data changes nothing. The fifth is asking an open-ended essay instead of a few tappable reasons, which kills response rate.
Key takeaways
- iOS has no uninstall callback, so catch churn intent earlier with exit-intent and delete-account prompts.
- Acquiring a new user costs around 5x more than keeping one, so churn insight pays for itself.
- Ask one kind, skippable question with a few tappable reasons; never block the user from leaving.
- Build the prompt from a free VP0 design, tag answers in analytics, and act on the top reasons.
Frequently asked questions
How do I add an uninstall survey to an iOS app? You cannot survey on uninstall on iOS, because there is no uninstall callback. Instead, ask at exit intent (delete-account tap, cancellation, long-dormant return) with a one-question prompt, and optionally send a web survey by email afterward.
Why can’t iOS apps detect uninstalls? Apple does not provide an uninstall event to apps, by design. Android allows an uninstall survey; iOS does not, so you rely on earlier signals.
Where is the best place to ask why a user is leaving? The delete-account flow, which you likely already have because Apple requires account deletion. It is the clearest moment of intent.
What should the exit-intent prompt ask? One question, “the main reason you are leaving,” with a few tappable options and an optional text field. Keep it short, respectful, and skippable.
Frequently asked questions
How do I add an uninstall survey to an iOS app?
You cannot survey on uninstall on iOS, because there is no uninstall callback. Instead, ask at exit intent (delete-account tap, cancellation, long-dormant return) with a one-question prompt, and optionally send a web survey by email afterward.
Why can't iOS apps detect uninstalls?
Apple does not provide an uninstall event to apps, by design. Android allows an uninstall survey; iOS does not, so you rely on earlier signals.
Where is the best place to ask why a user is leaving?
The delete-account flow, which you likely already have because Apple requires account deletion. It is the clearest moment of intent.
What should the exit-intent prompt ask?
One question, the main reason you are leaving, with a few tappable options and an optional text field. Keep it short, respectful, and skippable.
Part of the App Store Publishing, Build Errors & Deployment hub. Browse all VP0 topics →
Keep reading
User Feedback Survey UI That People Actually Answer
In-app surveys beat email only when contextual and short. Build a one-question survey, ask after a key action, and route happy users to the App Store rating prompt.
Win-Back Push Notification UI That Re-Engages Users
A win-back flow is push plus landing screen. Build the landing screen from a free VP0 design so the return delivers what the push promised, and deep-link the tap.
Account Deletion UX: Alternatives to Dark Patterns
Apple requires in-app account deletion. Build an honest, easy-to-find flow from a free VP0 design, and replace dark patterns with real options like pause or export.
How to Write an App Store Description That Ranks
On iOS the name, subtitle, and keyword field do the ranking; the description converts. Here is how to write both so your app gets found and downloaded.
App Store Preview Video UI: Convert in the First Frames
An App Store preview video must sell muted, in seconds. Build motion-graphic screens from a free VP0 design, lead with the value, and follow Apple's preview rules.
App Store Rejected? Design Fixes That Get You In
Most App Store design rejections come from a few rules. See the common reasons under 4.2 and 4.3, and fix them fast by rebuilding screens from a free VP0 design.