App feedback survey questions for the people who use your app
Twelve questions for the people who use your app, sent as a link after a release or a milestone.
- 12questions
- About 3 minto complete
The 12 app feedback survey questions
An app feedback survey is a short questionnaire you send to the people who use your app. It records their device, how they found the app, how satisfied they are, whether it crashed, whether a purchase felt worth the price and the feature they want next. Every question is ready to edit when you create your own survey.
About the user (4 questions)
Four quick taps that let you split every answer below.
- Which device do you use this app on?A bug on one platform stays hidden until you filter by device.
- How did you first find this app?
- How long have you been using this app?
- How often do you use this app?
Satisfaction and reliability (3 questions)
Three statements on one agree scale.
- Overall, I am satisfied with this app.
- This app is easy to use.
- This app works the way I expect it to.
Crashes and purchases (2 questions)
One answer for engineering and one for whoever owns pricing.
- Have you experienced a crash or a bug in the last 30 days?Send every Yes to engineering with the device answer attached.
- If you have paid for anything in this app, such as a subscription or an in-app purchase, was it worth the price?People who have paid nothing pick the third option.
Recommend, request and return (3 questions)
One typed request instead of a ranked list: the median respondent spends 25 seconds on a ranking question, and surveys containing one finish 7.2 points worse.[2]
- How likely are you to recommend this app to a friend or colleague?
- What is one feature or fix that would make you use this app more?
- How likely are you to still be using this app in three months?High satisfaction with a low answer here means liked, not needed.
How to use the app feedback survey
Send it to people who already use the app. Choose a moment just after they finished something, such as setup or a resolved support ticket. Apple times its own review prompt the same way, at the end of a sequence of events the person completed, and shows it at most three times in a 365-day period.[1]
The survey asks for no name or email, so tell people that when you send it. Split the answers by device and by time using the app before you read any average. Report satisfaction as the share who agree or strongly agree, and compare it release to release.
To score the recommend question, follow the NPS survey. A build still in testing needs the UAT questionnaire. A finance app needs the mobile banking survey. For a site people open in a browser, send the website feedback survey.
App feedback survey FAQ
What questions should an app feedback survey ask?
Ask which device people use, how they found the app, how long and how often they use it, how satisfied they are, whether it crashed, whether a purchase was worth the price, how likely they are to recommend it and which feature they want next.
How many questions should an app feedback survey have?
Twelve covers the device, satisfaction, crashes, purchases and one feature request in about three minutes. Eleven of them are quick taps and the single typed answer is optional, so someone on a phone can finish it in one sitting.
Can I link to the survey from inside my app?
Yes. Put the survey link behind a button or a menu item and it opens in the phone browser, so people answer on the same device they use the app on.
Does it work for software that is not a phone app?
The questions fit any app that people install or sign in to. For a tool your colleagues are trying out at work, the software evaluation survey asks whether it does the job and whether to keep it.
Michael Hodge, survey methodology · Updated 2 October 2026 · How templates are reviewed
Sources (2)
- Apple. Requesting App Store reviews. StoreKit developer documentation. developer.apple.com
- SuperSurvey Response Benchmark, 16 September 2023 to 25 August 2026: 25,112 surveys with 998,864 completions. Method note.
Find out what your users would fix first
Open the twelve questions in the editor and send the link after your next release.
Use this template