When Someone Deletes Your App, Ask One Good Question
Photo: Japanexperterna.se from Japan, CC BY-SA 2.0, via Wikimedia Commons
An uninstall is a strange kind of goodbye. There is no handshake, no reply, no chance to ask what went wrong. The icon disappears from a home screen and the data stops arriving. Most apps respond with silence. Some respond with a guilt trip. Neither teaches you anything.
The exit you can actually design
Let us be precise: on iOS and Android, you cannot reliably intercept an uninstall. Once the app is gone, your survey is gone with it. So the 'uninstall interview' is less a single screen and more a set of moments around leaving: account deletion, a 'taking a break' option, a trial that is about to end, or a web survey linked from a confirmation email. The point is not to trap people. The point is to make it easy for them to tell you why they are going.
This is different from a subscription cancellation flow. Cancellation is a commercial moment with legal and ethical weight. An uninstall interview is a research moment. It should not try to save the sale. It should try to understand the exit.
Ask less, learn more
A good exit flow has a three-question limit. In practice, one question is often enough.
Start with a single-choice reason. Keep the options short and human: 'Finished what I needed', 'Too expensive', 'Missing a feature', 'Too slow or buggy', 'Notifications were too much', 'Just not for me', 'Prefer not to say'. Add an optional text box for anything else, but do not make it required. If you want a second question, ask 'What would have made you stay?' and leave it open. Do not ask for a phone number, a meeting, or a detailed life story.
The wording matters. 'Sorry to see you go. One quick question before you delete your account?' is fine. 'Are you sure? You will lose 47 saved items and all your progress' repeated three times is not. The first respects the decision. The second punishes it.
Design the exit like a front door
The delete button should be where people expect it, not hidden behind a chat with support. The survey should be skippable. The final confirmation should be clear about what happens next: what is deleted, what is kept, and when. If someone asks to delete their account, do it. Do not make the survey a toll booth.
UK data protection rules apply here. Collect only what you need, explain why you are asking, and set a retention period for the responses. If you are using the feedback for product research, say so in plain English. A short line like 'We read every answer, but we cannot reply to each one' sets expectations without sounding corporate.
From replies to a monthly ritual
The value is not in the individual response. It is in the pattern. Once a month, pull the reasons into a simple spreadsheet or a tagged board. Count the categories. Read the free-text answers out loud in a thirty-minute review with product, design, and support. Pick one theme to investigate and one small change to make.
Look for clusters, not anecdotes. One person saying the app is too expensive is a data point. Eight people saying they only needed it for a one-off task is a positioning problem. Three people mentioning the same confusing step is a design problem. If the free-text answers are full of anger, read for the specific trigger, not the tone.
Pair the exit data with support tickets and cancellation reasons, but keep them separate in your head. A cancellation survey tells you about value and price. An uninstall or deletion survey tells you about fit, friction, and life changes. Both are useful. They are not the same conversation.
What not to ask
Do not ask for a net promoter score on the way out. Do not ask 'How can we improve?' as the only question; it is too broad to act on. Do not use a five-star rating widget that only accepts positive answers. Do not pre-tick a box that signs people up to marketing. Do not make the survey longer than the deletion itself.
And do not call it an exit interview if it is really a win-back trap. Users can tell the difference. A respectful exit flow says: thank you for trying this, tell us one thing if you have a moment, and here is the door. That is it.
A small script to steal
Screen one: 'Before you go, can you tell us why?' One choice list. Buttons: 'Send and continue' and 'Skip'. Screen two, only if they choose 'Other': 'Anything else we should know?' Optional text box. Final screen: 'Your account will be deleted on 15 November 2026. We have saved your answer anonymously.' Then a clear 'Delete my account' button.
That is not glamorous. It will not go viral. But it will give you a monthly stack of honest reasons from people who have already decided to leave. Those reasons are often more useful than the reviews from people who stayed.
An uninstall is not a failure of the relationship. It is the end of one. Ask one good question, listen without arguing, and let people go. The next version of your app will be better for it.