Survey · Feedback
Mobile app survey template
Starts with the one job people open the app for, then asks how easy that job is. Anyone who struggles is asked where they get stuck, and anyone who reports crashes or slowness describes the last time it happened, which is what your developers need. Users who want to test new features leave an email and get their own ending.
Try it live
Try it as a respondent
Every question, and where it leads
The conversation
What a respondent is asked, in order.
Hi! A few quick questions about the app. Your answers go straight to the people who build it.
Which phone do you use the app on?
How often do you open the app?
What's the main thing you open the app to do?
How easy is it to get that done?
Where do you get stuck or slowed down?
Have you run into any of these in the last month?
Tell us about the last time that happened. What were you doing just before?
How would you rate each of these?
What one change would make the app more useful to you?
How likely are you to recommend the app to a friend?
Would you like to try new features before everyone else?
Great. Which email should we send beta invites to?
Endings
Thanks for the feedback
You're on the beta list 🚀
The flow
Where each answer leads. Every route here is editable once the form is yours.
Single select
Single select
Short text
Opinion scale
Long text
Multi select
Long text
Matrix
Long text
NPS
Yes / No
What this template uses
- Single select
- Short text
- Opinion scale
- Long text
- Multi select
- Matrix
- NPS
- Yes / No
- 4 branches
- 2 endings
Questions to consider
- Will you show this inside the app, or send the link by email or push notification? In-app reaches active users, email reaches the ones who drifted away.
- Do you already know the app version and device from your analytics, or do you need to ask?
- Which problems in the checklist are ones you've seen in crash reports, and which are you guessing at?
- What will you give beta testers in return, and how many can your team actually support?
How to use the responses
Read the main tasks first and group them: the top few are what the app is really for, whatever the roadmap says. Compare ease scores across those groups to see which job is hardest. Pass every problem description to engineering with the platform attached, since a crash reported only on Android points somewhere very different from one on both. Invite the beta list before your next release.
How to customize and share it
- 1Rename the rows in the rating grid to the parts of your app people actually use, such as search, checkout or messages.
- 2Edit the problem list to match what shows up in your support tickets and crash reports.
- 3Share the link inside the app after someone completes a key task, or email it to users who haven't opened the app in a while.
Frequently asked questions
What questions should a mobile app survey ask?
What people use the app for, how easy that is, what goes wrong, and what they'd change. A recommendation score gives you a number to track between releases.
When is the best time to ask for app feedback?
Right after someone finishes a task in the app, while it's fresh. Avoid interrupting them halfway through something.
How do I get useful bug reports from users?
Ask what they were doing just before the problem. This survey only asks that of people who reported a problem, so everyone else skips it.
Can I embed this survey in my app?
You can share it as a link, which opens in the phone's browser or an in-app web view, or embed it on a website.