Would really like an option to ask if user is satisfied before rating

[rboisjoly]

If user doesn't like their experience, they could be prompted to send an email to support. If they are happy, then they can rate directly. Other similar frameworks offer such an option.

[coneybeare]

If they aren't satisfied, it should be caught by the logic you implement yourself in setting the significant events required, time required etc.

[rboisjoly]

I'll have to give this some thought... what is a significant event for one, might be a user trying the same thing over and over and failing, then you hit them with a review question... I don'f feel confident that my app makes it easy to set up a logic which would allow me to detect this. And frankly, trying to analyse what the user is doing might be something I would do later on... I offer the opportunity to send feedback, but am still wary of forcing them into a bad review by having this appear at the wrong time. I'm probably not getting the significant event concept...

[coneybeare]

Significant events, plus days till review prompt. It is unlikely that some would would still use an app x weeks and dozens of significant events after first launch. Most of my apps use 2 weeks, 10 runs and 20 significant events, but this will change for your specific app and usage patterns.

On Mon, Oct 7, 2013 at 8:44 PM, rboisjoly notifications@github.com wrote:

I'll have to give this some thought... what is a significant event for one, might be a user trying the same thing over and over and failing, then you hit them with a review question... I don'f feel confident that my app makes it easy to set up a logic which would allow me to detect this. And frankly, trying to analyse what the user is doing might be something I would do later on... I offer the opportunity to send feedback, but am still wary of forcing them into a bad review by having this appear at the wrong time.

I'm probably not getting the significant event concept...

Reply to this email directly or view it on GitHub: https://github.com/UrbanApps/UAAppReviewManager/issues/6#issuecomment-25857338

[rboisjoly]

That's ok for not asking for a review until these things happened. The problem is if a user is facing issues and decides he wants to blast it on the App Store... because he's not asking for help, misunderstood something, or the issue is totally unrelated to the app itself. The idea would be to intercept people having issues before they post to the App store.

Could make two things completely unrelated. After a couple of launches, ask user if all is ok and to feel free to contact us. Then, later, as they use it and hit the significant events, ask to review.

I guess the goal of your tool is not to intercept users with potential issues to avoid bad reviews as much as encouraging happy users to post good ones. I strive to do both. I'll think about ways to change my perception and see if a different logic applies.

I don't want to get into a philosophical debate and you seem to have your vision set on this way of doing things, perhaps with reason. I'll give it more thought.

Having some apps on the Mac since 2001, I've had my share of weird emails and reviews on various sites. And I've had users live with issues for a long time without reporting them and finally posting a review about an issue I was simply unaware of. Yet, they use the software every day and would have hit those significant events.

[coneybeare]

Apple deals with this by placing a Contact Support button next to the Leave a Review button in iTunes. Generally, a Contact Us button is very useful in the app, but is outside of the scope of UAAppReviewManager. It would be trivial for you to implement your own alert after querying the usage statistics in UAAppReviewManager to try and intercept unhappy users, but this would be answered by analytics in your software as only a small handful of users ever take to time to respond to anything.

On Oct 7, 2013, at 9:35 PM, rboisjoly notifications@github.com wrote:

That's ok for not asking for a review until these things happened. The problem is if a user is facing issues and decides he wants to blast it on the App Store... because he's not asking for help, misunderstood something, or the issue is totally unrelated to the app itself. The idea would be to intercept people having issues before they post to the App store.

Could make two things completely unrelated. After a couple of launches, ask user if all is ok and to feel free to contact us. Then, later, as they use it and hit the significant events, ask to review.

I guess the goal of your tool is not to intercept users with potential issues to avoid bad reviews as much as encouraging happy users to post good ones. I strive to do both. I'll think about ways to change my perception and see if a different logic applies.

I don't want to get into a philosophical debate and you seem to have your vision set on this way of doing things, perhaps with reason. I'll give it more thought.

Having some apps on the Mac since 2001, I've had my share of weird emails and reviews on various sites. And I've had users live with issues for a long time without reporting them and finally posting a review about an issue I was simply unaware of. Yet, they use the software every day and would have hit those significant events.

— Reply to this email directly or view it on GitHub.

[rboisjoly]

I have yet to have a user contact us using said button.

Really.

All I was asking for was an additionally step or button to do this. Just an alternative to reviewing which is to contact the developer. It is completely trivial to do my own.

Just stating this is not your goal is enough. Suggesting it is not useful or the right way to do it is unnecessary.

There is lots of discussion on how the App Store is broken for this. So one answer may not be all that is required and certainly the way things are now is not the only not the best solution for every situation.

Keep this closed. Won't bother you again.

Good night

Envoyé de mon iPhone

Le 2013-10-07 à 21:42, Matt Coneybeare notifications@github.com a écrit :

Apple deals with this by placing a Contact Support button next to the Leave a Review button in iTunes. Generally, a Contact Us button is very useful in the app, but is outside of the scope of UAAppReviewManager. It would be trivial for you to implement your own alert after querying the usage statistics in UAAppReviewManager to try and intercept unhappy users, but this would be answered by analytics in your software as only a small handful of users ever take to time to respond to anything.

On Oct 7, 2013, at 9:35 PM, rboisjoly notifications@github.com wrote:

That's ok for not asking for a review until these things happened. The problem is if a user is facing issues and decides he wants to blast it on the App Store... because he's not asking for help, misunderstood something, or the issue is totally unrelated to the app itself. The idea would be to intercept people having issues before they post to the App store.

Could make two things completely unrelated. After a couple of launches, ask user if all is ok and to feel free to contact us. Then, later, as they use it and hit the significant events, ask to review.

I guess the goal of your tool is not to intercept users with potential issues to avoid bad reviews as much as encouraging happy users to post good ones. I strive to do both. I'll think about ways to change my perception and see if a different logic applies.

I don't want to get into a philosophical debate and you seem to have your vision set on this way of doing things, perhaps with reason. I'll give it more thought.

Having some apps on the Mac since 2001, I've had my share of weird emails and reviews on various sites. And I've had users live with issues for a long time without reporting them and finally posting a review about an issue I was simply unaware of. Yet, they use the software every day and would have hit those significant events.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub.

[coneybeare]

I am sorry if I offended you somehow, it was not my intention. Hopefully you can use the tracking stats in UAAppReviewManager to help you with this feature.