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.