Originally created by @Jeehut on GitHub (Jan 18, 2015).
Here and here I saw two newer examples of such frameworks like this but they both have a great new addition to the classic approach of just asking users for a rating:
They add the ability to let users who don't like specific parts directly give feedback instead of rate the app. This has to advantages: It helps to get feedback from users to improve the app and leads to less negative ratings.
Could we add such a feature into Armchair as well? I would imagine an option named "enableTwoFactorProcess" and if the user chooses a low rating (or dislikes the app) then Armchair opens a specified email address to send feedback to as a default option. As an addition users might get an option to use their own feedback implementation.
What do you think?
Originally created by @Jeehut on GitHub (Jan 18, 2015).
[Here](https://github.com/leonardoobaptistaa/FeedbackMe) and [here](https://github.com/andrei200287/SARate) I saw two newer examples of such frameworks like this but they both have a great new addition to the classic approach of just asking users for a rating:
They add the ability to let users who don't like specific parts directly give feedback instead of rate the app. This has to advantages: It helps to get feedback from users to improve the app **and** leads to less negative ratings.
Could we add such a feature into Armchair as well? I would imagine an option named "enableTwoFactorProcess" and if the user chooses a low rating (or dislikes the app) then Armchair opens a specified email address to send feedback to as a default option. As an addition users might get an option to use their own feedback implementation.
What do you think?
This was on my to-do list eventually, but I can't say when I will have time to add it.
Bulletpoints
All strings need to be configurable, similar to the existing rating.
All default strings need to be translated into the existing localizations
Should be opt-in for backwards compatibility
Should include closures for the actions
Should not have stars, but more of a "Are you happy with the app?" feel.
Are you happy with APP_NAME?
Yes -> Existing rating prompt
No -> New contact prompt
Sorry to hear that. Would you like to talk to our team about it?
Email Us -> Open default email or closure action
No, Thanks -> Cancel
I would entertain pull-requests on this.
@coneybeare commented on GitHub (Jan 24, 2015):
This was on my to-do list eventually, but I can't say when I will have time to add it.
Bulletpoints
- All strings need to be configurable, similar to the existing rating.
- All default strings need to be translated into the existing localizations
- Should be opt-in for backwards compatibility
- Should include closures for the actions
- Should not have stars, but more of a "Are you happy with the app?" feel.
Are you happy with APP_NAME?
- Yes -> Existing rating prompt
- No -> New contact prompt
Sorry to hear that. Would you like to talk to our team about it?
- Email Us -> Open default email or closure action
- No, Thanks -> Cancel
I would entertain pull-requests on this.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Jeehut on GitHub (Jan 18, 2015).
Here and here I saw two newer examples of such frameworks like this but they both have a great new addition to the classic approach of just asking users for a rating:
They add the ability to let users who don't like specific parts directly give feedback instead of rate the app. This has to advantages: It helps to get feedback from users to improve the app and leads to less negative ratings.
Could we add such a feature into Armchair as well? I would imagine an option named "enableTwoFactorProcess" and if the user chooses a low rating (or dislikes the app) then Armchair opens a specified email address to send feedback to as a default option. As an addition users might get an option to use their own feedback implementation.
What do you think?
@coneybeare commented on GitHub (Jan 24, 2015):
This was on my to-do list eventually, but I can't say when I will have time to add it.
Bulletpoints
Are you happy with APP_NAME?
Sorry to hear that. Would you like to talk to our team about it?
I would entertain pull-requests on this.
@Jeehut commented on GitHub (Jan 24, 2015):
👍
@ryanio commented on GitHub (Jan 3, 2016):
+1, this would be fantastic