# Feedback — Mobile app In-app prompts that ask users for their opinion — NPS surveys, rating scales, and open text — surfaced at the right moment and at the right frequency. Source: https://www.checklist.design/mobile/feedback ## Items ### Prompt timing The moment at which the feedback request appears, chosen to follow a point of completed value rather than a fixed session count _Tip: The highest-quality feedback comes from users who have just done something successfully, since the experience is fresh and the sentiment is accurate. Asking after a failure, or on launch, produces noise_ ### Contextual trigger The specific in-app event or screen that initiates the feedback request, relevant to the question being asked _Tip: 'How easy was it to complete that payment?' asked immediately after checkout produces better signal than 'How do you feel about the app?' asked on the home screen_ ### Single-question entry Starting the feedback flow with one question rather than a form, to lower the barrier to responding _Tip: NPS surveys convert because they start with one question. Even if more follow, the initial commitment to a single answer gets users through the door, since the drop-off at step one is the most significant_ ### Rating scale A numeric scale (typically 0–10 for NPS or 1–5 for CSAT) as the primary feedback signal _Tip: Segment the follow-up question by score range. Promoters, passives, and detractors have different things to say, since a single follow-up question for all three produces averaged, less useful responses_ ### Open text follow-up An optional text field shown after the rating, inviting the user to expand on their score. _Tip: Mark it explicitly as optional and say so. 'Tell us more (optional)' outperforms an unlabelled empty field — users need to know they can skip before they will commit to the rating step._ ### Dismissal option A clear way to close the prompt without responding. _Tip: Label the dismiss action neutrally — 'Not now' rather than 'No thanks'. The user who dismisses today is still worth asking again in three months._ ### Frequency cap A limit on how often the same user sees a feedback request, regardless of how many trigger conditions are met. _Tip: Users who dismiss a prompt repeatedly are signalling disinterest — continued prompts push them toward frustration rather than response. Once per session is a reasonable maximum; once per month a reasonable minimum interval._ ### Submission confirmation A brief acknowledgement that the feedback was received before returning the user to their previous context. _Tip: A one-line thank you that disappears after two seconds is enough. What matters is that the user knows it landed — without confirmation, some will submit again assuming the first attempt failed._ ## License for the Checklist Design collection Checklist Design collection: https://github.com/Checklist-Design/skills Snapshot: bfae71e507b1b7c03c12e0756402b60eb80f5d14 · Imported: 2026-11-12 Republished under the MIT License. Original checklist text belongs to Checklist Design. MIT License Copyright (c) 2026 Checklist Design Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.