The weeks after launch are strangely quiet. People sign up, some come back, some disappear, and almost none of them tell you why. You open your analytics and see numbers without reasons. Knowing how to get user feedback for your app is what turns that silence into a list of things to fix.
Most founders try one of two things. They add a "Send feedback" button and wait, or they email every user a long survey and get three replies. Both feel like listening, and both mostly produce nothing. Good feedback is not something you collect once. It is a small, steady system: ask the right people, at the right moment, the right kind of question, and then show them you heard it.
This guide covers that system for a solo founder or a tiny team.
Why feedback after launch is different
Before launch, you talk to potential users about their problems. After launch, you have something better: real people using a real product. That changes what you should ask.
You no longer need opinions about an imagined app. You need to understand behavior. Why did this person stop after day two? What made that person upgrade? Which feature do people expect that you have not built? These are questions about what already happened, and people answer those far more accurately than questions about what they might do.
It also changes who to listen to. Your loudest users are not always your most important ones. The person who emails you five feature ideas a week may not represent the quiet majority who either stay or leave without a word.
The four sources worth your time
You do not need every feedback tool. You need these four, used together.
1. Short in-app questions at the right moment
A one or two question prompt inside the app, shown right after a meaningful moment, gets far more responses than an email survey. Vendors that sell survey tools commonly report in-app response rates somewhere between about 12% and 30%, with rates below 10% usually pointing to bad timing or a clumsy prompt. Treat those numbers as rough, but the direction is consistent: ask inside the app, ask briefly, ask at the right time.
The right time is just after a success: finishing onboarding, completing the core action for the first time, or hitting a milestone. Never interrupt someone in the middle of a task.
2. Conversations with a handful of users
Nothing replaces talking to people. Fifteen minutes on a call with five active users will teach you more than a hundred survey responses, because you can ask "why?" and follow the answer.
Invite people directly, by personal email, not through a form. Offer something small in return, like a free month. Then mostly listen. Ask them to walk you through the last time they used the app, step by step. The moments where they hesitate, work around something, or say "I wish" are where your best ideas live.
3. Exit and cancellation questions
The users who leave carry the most valuable information, and they are the hardest to reach. Catch them at the exit:
- When someone cancels a subscription, ask one multiple choice question about why, with an optional comment box. Keep it to one screen.
- When someone goes quiet, send a short, personal email after a week or two of inactivity: "I noticed you stopped using the app. Was something missing or confusing? A one-line reply helps more than you would think."
Exit answers are often blunt, and that is exactly why they are useful.
4. What people say without being asked
App store reviews, support emails, social media mentions, and messages in any community you run are all unprompted feedback. They are biased toward strong feelings, but they show you the words users actually use and the problems that bother them enough to speak up.
Read them weekly, and copy anything that repeats into one place.
When to ask (and when not to)
Timing decides whether you get an honest answer, a polite one, or none.
Ask right after the moment you want to learn about. If you want to know whether onboarding works, ask when onboarding ends, not two weeks later when the memory has faded.
Ask the right segment. New users can tell you about first impressions and confusion. Users who have been active for a month can tell you about value and missing features. People who just churned can tell you about the gap between what they expected and what they got. Do not mix these groups in one survey.
Do not ask too often. Set a rule, for example no more than one prompt per user every few weeks, and never on the first session before they have experienced anything.
Do not ask during friction. A feedback prompt that appears right after an error message will mostly measure frustration with the error.
Questions that get honest, usable answers
The wording of a question shapes the answer. A few principles go a long way.
Ask about past behavior, not future intent. "Would you use a calendar feature?" gets a polite yes. "What did you do the last time you needed to plan your week?" tells you whether a calendar matters.
Ask open questions, then one specific follow-up. "What almost stopped you from signing up?" or "What is the one thing you would change?" leave room for answers you did not expect.
Avoid leading questions. "How much do you love the new design?" tells people what to say. "How did the new design change how you use the app, if at all?" does not.
Keep it short. One rating question and one open text question beats a ten question form every time. If you need more, talk to people instead.
A few questions that consistently work:
- "What were you hoping this app would help you do?"
- "What is the main thing that is still missing for you?"
- "How would you feel if you could no longer use this app?" (very disappointed, somewhat disappointed, not disappointed)
- "What would you use instead if this app disappeared?"
- "What made you decide to cancel?"
The "how would you feel if you could no longer use it" question deserves special attention. The share of active users who answer "very disappointed" is a useful early signal of whether you have built something people genuinely need. Track it over time rather than obsessing over a single reading.
Turning feedback into decisions
Collecting feedback is the easy part. The hard part is not drowning in it, and not building everything people ask for.
Keep one simple log. A spreadsheet with columns for date, source, user type, the quote in their own words, and a short theme tag is enough. The tag might be "onboarding confusion," "wants reminders," or "price." Do not over-design it.
Look for patterns, not loud voices. Once a week, sort by theme. A problem mentioned by eight different users matters more than a feature one user mentions eight times.
Listen to the problem, not the proposed solution. Users are excellent at describing pain and often poor at designing fixes. When someone asks for a specific feature, ask what they were trying to do when they wanted it. The underlying need might have a simpler answer.
Weigh by who is speaking. Feedback from users who match your ideal customer and stay active should count for more than feedback from people who were never a good fit.
Pair feedback with numbers. Feedback tells you why. Analytics tell you how many. If users say onboarding is confusing and your data shows most drop off at step three, you have a clear priority.
Decide, then write down what you decided. For each recurring theme, choose one of three actions: fix it soon, investigate further, or deliberately do not do it. Writing down the "not doing" decisions saves you from relitigating them every week.
Close the loop
The fastest way to get more feedback is to show people that their last feedback mattered.
When you ship something users asked for, tell them. A short personal email to the people who mentioned it, a line in your changelog, or a note in the app that says "You asked for this" makes users feel heard and makes them far more willing to answer the next question.
Even when you decide not to build something, a brief reply explaining why builds trust. People rarely expect you to do everything they suggest. They do expect not to be ignored.
A simple weekly feedback routine
If you only have an hour a week, spend it like this:
- Fifteen minutes: read new reviews, support emails, exit answers, and in-app responses. Add anything meaningful to the log.
- Twenty minutes: have one short conversation with an active user, or send three personal emails inviting one.
- Fifteen minutes: sort the log by theme and pick the single most important problem for next week.
- Ten minutes: reply to people whose feedback led to a change.
Learning how to get user feedback for your app is less about tools and more about habit. A founder who listens a little every week will understand their users better than one who runs a big survey every quarter, and that understanding is what makes every other decision easier.
Originally published at https://foundyra.com/news/how-to-get-user-feedback-for-your-app
Top comments (0)