3

I'm considering to ask users in app for feedback on a specific feature, right after they used it. The goal is to have a) quantitative feedback on the feature and b) a list of comments from step 3 where I can see what people would like to see improved.

It would be a 4 step process,

  1. Non-blocking bottom sheet to ask for feedback
  2. Dialog with quantitative question (can be dismissed)
  3. Dialog with free-text question ("Why?", can be dismissed)
  4. Dialog to ask for data processing consent (GDPR)

enter image description here

I have seen similar approaches before, for example from Google Lens:

enter image description here

Are there any publications on how valid this kind of feedback is, and whether it has a negative effect on the user experience?

I find plenty of service providers who make these kinds of in-app dialogs, but so far no solid literature on their usefulness.

  • 1
    I am not sure about a published paper on this topic, but the general understanding is to have this sort of feedback after the user has become familiar with the app and has accomplished the task for which you would like gather feedback at least once. Also, I think the last screen about GDPR should not be included here as part of the feedback process. Asking user for permission could be part of the login process or contextual. – Ren Jun 4 at 11:20
  • Isn't asking for consent in this case highly contextual? As in, you give us information, and we ask that we can use it and connect it to other bits of information (like, how often you've used the feature you're giving feedback on)? – bootsmaat Oct 7 at 18:49
0

I found this article from NNg about the Exit intent popups pretty relevant to your question.

  • How? I'm asking about in-app feedback. – bootsmaat Nov 22 at 17:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.