Usertick
App update survey template

See whether your update made the app better, from the people using it

Three questions for the second session after a release: whether users noticed what changed, how the app feels compared with before and anything that stopped working. Usertick reads every written answer and flags the ones that report a bug.

What this app update survey tells you

An app update survey asks users how a release landed once they have used it a little. This template takes about 45 seconds: a yes or no on whether they noticed the changes, a dial from much worse to much better, and an open question on anything that stopped working.

It is written for the second session after an update, once the first session was spent finding what moved. In a web app, a custom event your code fires each session after a release, with calls needed set to 2, opens it on the second (from Starter, or on 1 survey on Free). Inside a phone app, have the app open the survey's link on the second launch of a new version, with the version added to the link as a tag.

Usertick reads each written answer, files it under a category such as speed and reliability or features and gaps, and gives each response an urgency, so a broken feature after a release reaches your team first. Results shows the share who noticed the changes, the dial's five stops from much worse to much better with the share of each, and every written report, against the period before.

On your websiteAs a linkIn an emailAs a conversation
Questions
3
Time to answer
About a minute
Written for
The second session after an app update
Plans
Every plan, the free plan included

See it on every channel

The same template on your website, behind a link, in an email and as a conversation.

On your website

Show it as a popup, a side button or inside the page, and choose the pages and the moment it opens: on page load, after a delay, on scroll or as someone is about to leave, on every plan. Event and behavior triggers work on 1 survey on Free and on every survey from Starter.

The 3 questions, one by one

What each question asks, why it is there, what it shows you and what to change.

Question 1 of 3 · Yes / No

Did you notice what changed in this update?

Why ask it
If users didn't notice what changed, your release notes missed them, and their answer to the next question is about the app as a whole.
What you learn
Results shows the share that said yes, against the period before. Select No to see how users who missed the changes rate the app.
Make it yours
Name the headline change in the label, such as the new search, when one change matters most.
Question 2 of 3 · Mood dial

Compared with before the update, the app feels

Why ask it
A dial from much worse to much better asks for a comparison, which is the question every release raises, and five stops keep it to one move.
What you learn
Results shows the five stops from Much worse to Much better, each with its share, against the period before. Select Worse or Much worse to filter the page to those users and read what stopped working.
Make it yours
Check the share of Worse and Much worse in the first days after each release, while a rollback or a quick fix is still easy.
Question 3 of 3 · Text · Optional

Did anything stop working?

Why ask it
A release can break something users rely on, and this question catches it in their words while the update is new. It is optional, so users with nothing to report still finish.
What you learn
Each answer appears with its sentiment and theme, filterable by theme, with up to 8 themes and their trends, so a feature that broke for many users shows up as one growing theme.
Make it yours
Set a workflow (every plan) that posts high urgency answers to Slack or Microsoft Teams, so the team on call sees broken features the day the release ships.

What the answers show

Results turns each question into numbers you can follow week by week.

Every written answer, read for you

Each answer arrives with its category, theme, type and urgency, so the urgent ones reach your team first.

Use this template in four steps

From the template to the first answers.

  1. 1

    Open the template

    Sign up free and pick After an update in the template gallery. It opens in a matching style, ready to change.

  2. 2

    Make the questions yours

    Reword any question, change the options, and add logic or more questions.

  3. 3

    Choose where it runs

    Show it on your website, send it by email, share its link and QR code, or switch it to a conversation.

  4. 4

    Publish and read the answers

    Answers arrive in Results and the inbox as people send them, each written one read and filed by Usertick.

Tips for this survey

Small choices that keep people answering and the answers useful.

  1. 01

    Ask on the second session

    The first session after an update is for finding what moved. Ask on the second, when users can judge the change.

  2. 02

    One copy per major release

    Duplicate the survey for each major release, so every version has its own Results and the comparison stays clean.

  3. 03

    Tag the version

    When your app opens the survey's link, add the version as a tag, such as ?version=5.1, so each answer keeps it in workflows and Google Sheets.

  4. 04

    Close the loop in release notes

    When a fix ships for something users reported, say so in the next release notes, and mark each of those reports with a status in the inbox.

More product feedback templates and questions

Templates like this one, and single questions from the library to add to it.

ProductApp feature requestCollect feature ideas from inside the app, along with how often people would use them. Keep it in the app's settings or help menu.
ProductAppearance settingsFind out which appearance people use and which screens still look wrong in it. Show it after a design update.
ProductHome screen widgetLearn whether users have added your widget, what it should show and how often they look at it. Show it a week after the widget ships.
ProductOffline useFind out what users need to do without a connection and how well syncing works when they're back online. Show it after the app reconnects.

Questions from the library

Browse the question library
  1. How did you answer that request?Multiple choice · Permissions after an update
  2. Why did you say no to a permission?Text · Permissions after an update
  3. How does the app feel since the update?Mood dial · Updates and releases
  4. What changed for you after updating?Multiple choice · Updates and releases

Frequently asked questions

On the second session after the update, once users have had one session to find what changed. Ask once per release.

Usertick runs on websites and in web apps, so a phone app opens the survey's link on the second launch of the new version. In a web app, a custom event from your code opens it (from Starter, or on 1 survey on Free).

Select Worse and Much worse in Results and read what those users say stopped working. Fix the theme that comes up most, and compare the dial with the period before after the next release.

Then the update didn't reach them. Make the main change visible in the app, such as a short note on first open, and ask again after the next release.

Yes. Every card in Results compares with the period before, and a separate copy of the survey per release gives each version its own Results.

Yes. Every template comes with every plan, the free plan included, and the free plan covers 150 responses a month across your surveys.

Yes. The template becomes your own survey, so reword any question, add or remove questions, and change the options and the logic. The gallery stays as it is.

Yes, from Starter. The template is written in US English. Add languages by hand or with AI translation, and each person sees the survey in their browser's language.

Listen better, act faster, and build what truly matters.

Start free, see what your customers mean, and get each answer to the person who can act on it.

  • 150 responses a month on Free
  • Every channel and AI analysis
  • No card needed