Free survey template

App feedback survey template. Eleven questions on how your app works for the people who use it.

The device, how often people open the app and for what, a star rating, how easy it is, whether it crashed in the last 30 days, the feature they want next and how likely they are to recommend it. Users without crashes skip the bug report, and those who don’t want a reply finish before the email field.

Use this template

Free plan: 100 responses a month and up to 50 surveys, no credit card.

The template’s real survey on a phone.

  • 11 ready questionsAbout 2 min on a phone.
  • Yours to changeQuestions, answers and logic.
  • A ready reportA chart for every closed question.
  • Export on every planCSV, Excel and SPSS.

Store reviews come from the happiest and the angriest users. A survey hears from the ones in between, and tells you why.

The 11 app feedback survey questions in this template.

In the order users meet them. Replace [App], put your app’s main tasks in place of [Task 1–3] and add what you need.

How they use it

  1. Which device do you use [App] on most?

    Single choice Required

    • iPhone
    • Android phone
    • Tablet
    • More than one device

    Why ask it. Splits ratings and bug reports by platform. A low score on one platform points at that build, not at the app as a whole.

  2. How often do you use [App]?

    Single choice Required

    • Several times a day
    • About once a day
    • A few times a week
    • A few times a month
    • Less often

    Why ask it. Separates daily users from occasional ones. Their wishes differ, so read the feature requests by group.

  3. What do you use [App] for most often?

    Single choice Required

    • [Task 1]
    • [Task 2]
    • [Task 3]
    • Other, in their own words

    Why ask it. Put your app’s real jobs in place of the three placeholders. The report then shows which job brings the happiest users and which the least happy.

Rating, ease and bugs

  1. Overall, how would you rate [App]?

    Rating 1–5 Required

    Why ask it. A five-star rating in the same form as a store rating, but from users you invited, not only from those who chose to write a review.

  2. How easy is it to do what you need in [App]?

    Single choice Required

    • Very difficult
    • Difficult
    • Neither easy nor difficult
    • Easy
    • Very easy

    Why ask it. Ease of use on a labeled five-point scale. Read it with the main task to see which job is the hardest to get done.

  3. In the last 30 days, has the app crashed, frozen or shown an error?

    Yes / No Required

    • Yes
    • No

    Why ask it. The share of users who hit a problem in the last month. A No skips the bug report.

  4. What happened?

    Open answer Required What were you doing when it happened? If you can, add your phone model and the app version.

    Why ask it. A bug report in the user’s words. The hint asks for the phone model and the app version, because the survey does not read them by itself.

What comes next

  1. What one feature or improvement would you like to see next?

    Open answer

    Why ask it. One wish per user keeps the answers specific. The most repeated wish is a strong candidate for your roadmap.

  2. How likely are you to recommend [App] to a friend or colleague?

    NPS scale 0–10 Required 0 – Not at all likely, 10 – Extremely likely

    Then one open question, depending on the score:

    • 0–6 What disappoints you most about the app?
    • 7–8 What would make it a 10?
    • 9–10 What do you like most about the app?

    Why ask it. The Net Promoter Score of your app. Each group gets its own follow-up, so detractors say what disappoints them and promoters what they like most.

  3. May we contact you about your feedback?

    Yes / No Required

    • Yes
    • No

    Why ask it. Asks before you follow up on a bug or a wish. A No ends the survey here.

  4. Your email

    E-mail Required So we can follow up on your feedback.

    Why ask it. Where your team writes back about a bug or invites the user to try a new feature. Only users who said yes see it.

Use this template

How to set up an app feedback survey from this template.

  1. 1

    Copy the survey

    Click “Use this template” and create a free account or log in. The survey is copied to your account with all eleven questions and both jump rules. The copy waits in your survey list as a draft.

  2. 2

    Make it yours

    Replace [App] and put your app’s three main tasks in place of [Task 1–3]. The template comes with its own design; on Basic and higher you can change its colors, fonts and background in the survey’s design settings.

  3. 3

    Share it with your users

    Open the survey link from a button in the app’s settings or help screen, send it in your newsletter or show its QR code. It opens in the phone’s browser or in your app’s web view.

  4. 4

    Read the answers

    The report shows the stars, the ease scale and the NPS with its three groups. Turn on email notifications to read each bug report as it arrives.

How to read app feedback survey results.

Scores by platform

On Basic and higher plans, filter by device to compare the stars, ease and crashes on iPhone and Android.

Bugs to fix first

The share of Yes answers to the crash question is your problem rate for the month. The “What happened?” answers name the screens to check first.

Wishes by user type

Export everything to Excel, CSV or SPSS on any plan and sort the feature requests by how often people use the app.

How to get more users to answer.

  1. Ask people who know the app

    Send the survey to users after their first few weeks, not on day one. A new user can’t rate what they haven’t used yet.

  2. Ask everyone, not only fans

    Send the link to all active users. Asking only happy users for store reviews goes against app store rules, and it hides the problems you need to hear about.

  3. Tie answers to accounts

    On Basic and higher plans, pass the user ID or the app version through the link into a hidden field. Each answer then arrives with its account and version.

  4. Close the loop

    When you ship a requested feature or fix a reported bug, write to the users who left an email. They are the first to try it.

More app feedback questions you can add.

Not in the template. Add any of them in the builder in a few clicks.

Getting started

  • How did you find out about [App]?
  • How easy was it to get started?
  • What almost made you stop using [App]?

Features

  • Which feature do you use most?
  • Which feature do you never use?
  • How useful are the notifications?

Value

  • Which other apps do you use for the same job?
  • How would you feel if you could no longer use [App]?
  • Would you pay for extra features?

Questions about this template

What should an app feedback survey ask?

The device, how often and what for people use the app, an overall rating, how easy it is, whether it crashed recently, the feature they want next and how likely they are to recommend it. This template asks all of it in eleven questions, with an optional follow-up by email.

How do users open it from the app?

Through the survey link: a button in the app, a push message or an email opens it in the phone’s browser or in your app’s web view. There is nothing to install in the app.

Does the survey detect the phone model or app version?

No. The bug question asks the user for them. On Basic and higher plans you can pass the app version or a user ID through the link into a hidden field.

Can I ask happy users to rate the app in the store?

Send the survey to all users, not only to happy ones. App stores don’t allow review requests that go only to users who are likely to leave a good rating.

Does it work on the free plan?

Yes. Every question type in this template works on Free, including the star rating, the NPS with follow-up questions and both jumps.

Hear what your users want next.

Copy the survey, add your app’s tasks and put the link in your app.