In this guide
Closing the loop means telling the person who gave feedback what happened to it: fixed, planned, or declined. It costs a few minutes and it changes how people treat you next time. I have no figures on the effect, but the reasoning is simple: people who see that feedback gets read tend to write more carefully, and people who hear nothing tend to stop.
What to tell, and when
- Received (optional, only if the reply is not instant): "Thanks, I have it."
- Fixed: the change, the version, how to see it.
- Planned: roughly when, without a hard date you cannot keep.
- Declined: the reason in one sentence. A clear "no" beats silence.
- Needs more: one specific question.
Templates (Example texts)
Fixed
Hi [name], thanks for reporting that [problem]. It is fixed in version [x.y]. If you still see it, tell me your device and steps.
Planned
Thanks for the idea of [feature]. It is on my list for the next few releases. I will let you know when it ships.
Declined
Thanks for suggesting [feature]. I am not going to add it because [reason, e.g. it does not fit the app's purpose]. I appreciate you taking the time.
Need more
I could not reproduce [problem]. Which device and OS version were you on, and what did you tap just before?
Where to report back
- Directly to the person (email, reply in the tool they used). Best for bugs.
- Release notes: name the change in plain words ("Fixed the crash when opening a saved list") instead of "bug fixes".
- Public changelog or community post for patterns many people raised.
Do not ask for a store review as a thank-you, and do not offer anything in return for one. Store reviews are the user's free choice.
Keep it light
- Batch replies into your weekly triage.
- Keep three or four templates and edit them each time.
- Only promise what you will do.
- Do not publish someone's feedback or name without permission.
With AppReviewX
Feedback on AppReviewX is private and structured. Replying to your testers by thanking them and saying what you changed is good practice; their next feedback tends to be sharper. One feedback you write earns one credit. Start free.
Related: feedback bias, feedback from non-native speakers, hub.