Form questions
App feedback questions to ask before the store prompt
Ask 6 to 8 in the app, triggered after a completed task rather than on launch. Never skip the overall rating, whether the app has crashed recently and the one thing that is missing. Those three separate unhappy users with a bug from users with a gap, and they tell the team what to fix first.
App feedback questions asked inside the app catch problems while the user can still be helped, before they become a one star review. These twenty two questions cover the overall rating, what people use the app for, crashes and speed, what is missing and the device, so a bug report and a feature request never land in the same box.
The questions
Overall
Overall, how would you rate the app?Single choiceRequired
One to five stars as five options. Ask it first so the answer is not coloured by the questions about crashes.
How likely are you to recommend the app to a friend?Single choice
0 to 10 as eleven options, if you track a recommendation score.
How long have you used the app?Single choice
Less than a month, one to six months, six to twelve months, more than a year.
How often do you open it?Single choice
Every day, a few times a week, a few times a month, rarely.
What you use it for
What do you mainly use the app for?Multiple choice
Write the options in the words users use, not the names of internal features.
Which screen do you use most?Dropdown
Is there anything you used to do in the app that you now do elsewhere?Long text
Finds silent churn that a rating never shows.
Problems
Has the app crashed or closed on its own in the last week?Single choiceRequired
No; once; two to five times; more than five times.
How does the app feel for speed?Single choice
Fast, fine, slow on some screens, slow everywhere.
Which screen was slow or broke?Dropdown
Only useful if the crash answer was not No; in a conversational form, put it on its own screen.
A screenshot of the problem, if you have oneFile upload
Have you lost any data or work in the app?Single choice
What is missing
What is the one thing missing that would make the app better for you?Long textRequired
One thing, not a list, so answers can be counted.
How would you rate each of these?Rating grid
Rows such as ease of finding things, reliability, speed, design. Columns poor to excellent.
Have you contacted support about anything?Single choice
How satisfied were you with the reply?Single choice
About your device
Which phone do you use?Dropdown
iPhone, Android phone, iPad, Android tablet.
Which version of the app are you on?Short text
Show users where to find it, usually in Settings.
Which operating system version?Short text
Can the team contact you about your answers?Single choice
Email, if you said yesEmail
A conversational form supports an email field.
Anything else you would like to say?Long text
Which questions to make required
Three are required: the overall rating, the crash question and the one missing thing. Together they decide what happens to the answer, whether the user goes to support, to the bug queue or to the roadmap. Everything else is optional, because an in app survey competes with whatever the user opened the app to do and each required screen costs completions.
- Overall, how would you rate the app?
- Has the app crashed or closed on its own in the last week?
- What is the one thing missing that would make the app better for you?
The form built from these questions
A static copy of the finished form, from its own example page.
Three ways to change this bank
For a web app, swap the device section for browser and screen size, and drop the store review idea entirely. For a game, ask about difficulty, how far the player has got and whether purchases felt fair, and keep the crash question exactly as it is. For a paid business app used by a team, add the person's role and whether they chose the app or were given it, since buyers and users want different things.
Questions people ask
When should an app ask for feedback?
After the user finishes something, such as saving a route or completing an order, rather than on launch or in the middle of a task. A user who has just succeeded gives calmer, more useful answers. Avoid asking more than once every few weeks, or the prompt becomes the thing people complain about.
Should app feedback come before a store rating prompt?
Many teams ask a short in app question first and route unhappy users to support. Store rules on prompting reviews are strict, so do not use the survey to filter who gets asked for a public review in a way the store forbids. Check the current guidelines of each store before linking the two.
How do you separate bugs from feature requests?
Ask about crashes and speed in their own questions, and ask for the missing thing separately. A user who says the app crashed twice this week has a bug; a user who wants offline maps has a feature request. Mixing them in one open box makes both harder to count.
How many questions should an in app survey have?
As few as get the answer: six to eight is plenty for most apps, and three can be enough for a quick pulse. People open an app to do something else, and every extra screen loses some of them. Rotate optional questions between survey waves rather than asking them all every time.
Can screenshots be collected with app feedback?
Yes. A file upload question accepts images, and many users will share a screenshot of an error if asked. Make it optional and say what it is for. A screenshot of the exact error saves a support agent several messages back and forth.
What should the team do with the answers?
Route crash reports to the bug queue with the device and version, send low ratings with contact consent to support, and count the missing features each month. Share the top three missing things with the product team. Then tell users what changed, which makes the next survey more likely to be answered.
Build this form in about a minute
The button opens the form generator with this form already described. Change the wording to match your own, generate, then edit any field.
Create a form with OneCraftOther question banks
Customer interview questions for discovery calls
Customer interview questions for discovery should ask about what people did recently, not what they would do in the future, because past behaviour is the best evidence of a real problem. These twenty three questions run in five stages and are captured by the interviewer in a form, so every call produces notes in the same shape.
Pricing survey questions including the Van Westendorp four
Pricing survey questions ask what people spend now, what they would consider too cheap and too expensive, which plan they would choose and which features they would pay for. These twenty questions centre on the four Van Westendorp price sensitivity questions, asked in a fixed order after people know what the product does.
Concept testing survey questions from appeal to intent
Concept testing survey questions measure how people react to an idea before it is built: whether it appeals, whether it feels new, whether the claims are believable, what they would pay and whether they would buy. These twenty two questions follow that order, with screening first so the reactions come from the right people.
On writing the questions themselves, read How to collect customer feedback: five channels compared. For everything the builder can do, see the form maker. Step by step: Create a conversational form with AI, then View, export and manage your responses.
Written and checked by the OneCraft team. Last checked .