Originally created by @filipandrei87 on GitHub (Nov 19, 2015).
In many of my apps, the owner requested that the app review popup shows in specific scenarios: The user viewed "x" number of screens, and has gone through one/more specific actions.
You can't cover these cases just by using a generic significant event. Because of this, I'd have to override the behaviour for Armchair and only trigger the popup manually, when all conditions are met, thus a lot of code to handle.
A good solution would be to use events per category and add the minimum number of each category in order to trigger the popup.
Thanks
Originally created by @filipandrei87 on GitHub (Nov 19, 2015).
In many of my apps, the owner requested that the app review popup shows in specific scenarios: The user viewed "x" number of screens, and has gone through one/more specific actions.
You can't cover these cases just by using a generic significant event. Because of this, I'd have to override the behaviour for Armchair and only trigger the popup manually, when all conditions are met, thus a lot of code to handle.
A good solution would be to use events per category and add the minimum number of each category in order to trigger the popup.
Thanks
I would entertain a pull request with this behavior, but only if the default behavior is as it exists now, without categories and without any code changes.
@coneybeare commented on GitHub (Dec 1, 2015):
I would entertain a pull request with this behavior, but only if the default behavior is as it exists now, without categories and without any code changes.
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 @filipandrei87 on GitHub (Nov 19, 2015).
In many of my apps, the owner requested that the app review popup shows in specific scenarios: The user viewed "x" number of screens, and has gone through one/more specific actions.
You can't cover these cases just by using a generic significant event. Because of this, I'd have to override the behaviour for Armchair and only trigger the popup manually, when all conditions are met, thus a lot of code to handle.
A good solution would be to use events per category and add the minimum number of each category in order to trigger the popup.
Thanks
@coneybeare commented on GitHub (Dec 1, 2015):
I would entertain a pull request with this behavior, but only if the default behavior is as it exists now, without categories and without any code changes.