Update questions that show what each release changed for users
Ask users what they noticed after an update, what broke or improved and what they want next. Each question below comes with when to ask it and what the answer tells you.
What app update survey questions tell you
App update survey questions ask users what changed for them after a release: whether they noticed anything new, what broke or got better, whether the release notes helped and how far they trust the next update. Ratings and crash numbers move after a release, and these answers tell you which change moved them.
Ask within a week of a release, once most users have the new version. Usertick doesn't run inside phone apps, so open the survey's link from the screen that shows your release notes, email it to users, or ask on your web app. Tag the link with the version, and pick three to five questions.
Each written answer is marked as a bug, idea, complaint, question or praise, with a theme and a sentiment, so a regression reported in the first days reaches the team with an urgency. On every plan, a workflow can post new answers to Slack or Microsoft Teams for the release channel.
- Questions
- 12
- Best asked
- Within a week of each release
- Industry
- Mobile apps
- Where to find them
- From library in the Usertick survey editor, on every plan
The 12 updates and releases questions, with when to ask each
Grouped by what they tell you. Use them as they are or change the wording.
How the last update landed
Ask how the app feels since the update and what changed, then read the open answers for the cause.
- 02Mood dial
How does the app feel since the update?
How the app feels since the update, on a mood dial. Results shows each face with its share, and the comparison with the period before shows whether the release moved the mood.
- 12Emoji
How did the last update make you feel?
How the last update felt, on five faces. Use it in place of the mood dial when you want a simpler control, and follow the share of happy faces from one release to the next.
- 01Yes / No
Did you notice anything new after the last update?
A yes or no on whether the update was noticed at all. A high share of No after a feature release tells you the change needs a better introduction inside the app.
- 03Multiple choice
What changed for you after updating?
One answer that sorts users into better, broken, slower, different or unchanged. Select the broken answer in Results to read only those users' answers and find the regression.
- 05Text
What broke or improved for you?
The open question after the change, for breaks and wins alike. AI reading marks each answer as a bug, praise or another type, so broken things are easy to separate from the thanks.
Release notes and trust
These two show whether users hear about your changes and whether they believe the next update will go well.
- 04Stars
How useful were the release notes?
Rates the release notes on five stars. A low rating beside a high share who noticed nothing new means the notes aren't reaching users or aren't saying enough.
- 08Big scale
How much do you trust updates not to break things?
How much users trust updates not to break things, from 1 to 10. Ask it a few times a year, and treat a falling average as a sign to test more before release.
How users install updates
Update habits tell you how long an old version stays in use and how fast a fix reaches everyone.
- 06Yes / No
Do you update automatically?
Whether updates install by themselves for this user. Select No in Results to see how often manual updaters fall behind, which matters when you plan to drop an old version.
- 11Dropdown
How soon do you install updates?
How quickly users install updates, from right away to avoiding them. The share who wait until forced tells you how long old versions will stay in use.
What to ship next
Ask what users want in the next update and how they like change to arrive, before you plan the release.
- 07Multiple choice
What do you want in the next update?
Lets users tick what they want in the next update. Results shows a bar with the share for each, a wish list to set beside your roadmap.
- 10Ranking
Rank what matters in an update
Users put stability, features, speed, design and battery in order. Results shows the average place per item, which settles what a release should lead with.
- 09This or that
For new features you prefer
Two pairs: fewer polished features or more, faster ones, and opt in or on by default. Results shows a split bar per pair, a direct read on how users want change to arrive.
Tips for asking about updates and releases
Small choices that get honest, useful answers.
- 01
Ask within a week
Send the survey once most users have the new version. Sooner, you hear only from users who update right away.
- 02
Tag the version on the link
Add the version number as a tag on the survey link and change it each release. The tag stays with every answer.
- 03
Keep the same core questions
Ask the same three questions after every release. Results compares each card with the period before, so one release reads against the last.
- 04
Send regressions to the team
On every plan, a workflow can open a Jira or Linear issue from a response, so a break reported on day one gets a ticket the same day.
Add these questions to a survey
From the library to the first answers.
- 1
Open the library
In the Usertick survey editor, choose From library, filter by industry and topic, and add several questions at once.
- 2
Or paste your own list
Paste questions reads up to 10 questions from any text on Free, 100 on Starter and 200 on Pro and above, keeps your wording and picks an answer type for each.
- 3
Choose where it runs
Show the survey on your website, send it by email, share its link and QR code, or switch it to a conversation.
- 4
Read the answers
Results counts every score and choice, and Usertick reads each written answer and files it by topic, on every plan.
Templates and more questions about updates and releases
Full surveys that ask about the same things, and neighboring topics in the library.
Templates
Browse all templatesFrequently asked questions
Within a week of a release, once most users have it. Schedule the email up to 30 days ahead so it goes out on the day you choose.
Ask the same questions each time and change the version tag on the link. Results compares each card with the period before, and the tag is kept with each answer for Google Sheets and the API.
Three to five. Start with what changed, add the mood dial or the release notes rating, and end with the open question about what broke or improved.
Usertick doesn't run inside phone apps. Open the survey's link from the screen that shows your release notes, or show the survey as a popup on your web app.
Yes. The question library comes with every plan, the free plan included, and the free plan covers 150 responses a month across your surveys.
Yes. Once a question is in your survey, reword it, change its options or its answer type, and add logic to skip it for some answers.
Yes. The library is translated into Usertick's built-in languages, and in any other language it shows in English for you to translate.
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