Dynamic feedback reminder
The current release of Soundscape Community app features a pop-up on first opening it which invites the user to feedback on the 'vicinity distance' feature. The issue is that it appears before the user has had the opportunity to use it, and it does not make it easy for them then to provide any feedback on it. In addition to the Feedback option from the menu drop-down, this issue is about providing a more dynamic feedback reminder to the user. Key considerations include:
- Allowing the user to cancel the pop-up screen so they do not get the notification again (at least on the current installation!)
- Pop-up appearing after approx 5-7 sessions
- Making it easy to provide feedback, e.g. a rating scale for a particular feature, with supporting text field for additional details
is this only when you first download the app because when I just opened the app on my phone i did not get that pop up? I would be willing to look into this issue I just am not sure how to view that pop up.
Thanks @MBtheOtaku I see that my initial note is not entirely clear on the behaviour! What we're looking for is to not have the feedback pop-up appear on first use after downloading and opening the app, but to have it appear after about 5 separate sessions, and for it to have a rating scale of 1-5 stars, and an open text field for any other feedback. Hope that helps clarify...
I'm going to start working on this issue!
I started working on this issue by creating a new Helper file similar to AppShareHelper and AppReviewHelper which handle the pop-ups for sharing or reviewing the app. I was wondering what would be the best way to store user responses? Is there some sort of API to use to receive the responses? Or should I use GDATelemetry? I noticed it says it's a stub, but still seems to be used.
There's not currently any mechanism for receiving user data. The GDATelemetry subsystem was not included in the open-source release provided by Microsoft, and we never hooked up a replacement, so all the references you see to it in the code are no-ops. Getting a working telemetry system would be a nice project on its own, though at the same time I'm quite happy not having us handling any user-provided data and the security/privacy implications that come with that.
As for the feature at issue here, the current feedback link just opens a new email message in the user's email program. Keeping this as the mechanism could be fine for a first pass while we're focusing on improving the UX of when/how the prompt gets shown.