• Replies 25 replies
  • Subscribers 18 subscribers
  • Views 6414 views
  • Users 0 members are here
Options
Related

Suggestions for improvements to user review process and flagged reviews

r.485
over 5 years ago

"Thieves""

$@#$""

Impossible to uninstall"

"It doesn't work" (without any details)

These are some samples of reviews written for some of our apps. I have been flagging these types of comments, but since some time ago @Garmin is simply neglecting the flags :-(

Anyway, I think it'd be nice to reconsider the review approach to keep the store clean, friendly and useful for both developers and users.

Suggestions:
- Block offensive words
- Add some intelligence to suggest some actions from the user (e.g. "can't uninstall" => "All apps can be uninstalled" => "select another watch face using the watch menu before you try").
- 1 and 2 star reviews: suggest contacting developer to report a problem.

  • over 5 years ago in reply to r.485

    We did some checking, and it turns out this aspect of our store admin broken! When we mark a flagged comment for removal, it doesn't get removed. Expressionless

    I can assure you, however, that my team is handling the flagged comments as I described above. I've already talked with the store team, and they plan to get it addressed soon. Apologies for all of the confusion!

  • over 5 years ago in reply to Brandon.ConnectIQ

    Hi Brandon

    It seems that it isn't fixed yet. Could you please check? Will you let us know when it's solved?

    Thanks

  • Former Member
    Former Member over 5 years ago in reply to r.485

    Hi r.485, we’ve reached out on this issue (CIQSTORE-1671) and we’re expecting it resolved sometime in Q1. We apologize for the trouble this has caused and thank you for bringing this to our attention.

  • over 5 years ago in reply to Former Member

    I’ve also flagged some reviews which are blatantly showing the user itself is lazy to read and then gets all angry when the app doesn’t do what he wants. 

    Ive flagged it and it’s still haven’t been taken down. 

  • over 5 years ago

    This problem has been fixed--I just tested it to be sure, and it's working as expected. Flag away, folks!

  • over 5 years ago in reply to jim_m_58

    I agree with Jim. Contact developer NEEDS to have an email specified. (If the user gives a bogus email. Oh well)

    currently, all contact developer w no email I will just have to ignore. (And it’s usually a cannot do x or y w the app and no way to do next steps. Even worst if the error doesn’t show up in ERA - and I have to say ERA is at least better than not knowing if there are crashes)

  • over 5 years ago in reply to Nikeow

    This was something that was debated early on when we were developing the store administration tools, and I remember that an optional email is the intended design, but I don't remember the reasoning. I seem to recall taking the same position as you, so I'm willing to raise the question again and see what happens. Just to set the right expectation, I suspect this will not change, but it's worth checking. Slight smile

  • over 5 years ago in reply to Brandon.ConnectIQ

    Sure. That’ll be great in the meantime.. continue to ignore. Rofl 

  • over 5 years ago in reply to Brandon.ConnectIQ

    Actually, now that I'm thinking about it a little more, I'm 99% sure that we don't require this because of privacy concerns. Someone expecting a response *should* leave an email, but we wanted to preserve the ability to send feedback without providing any identifying information.

  • over 5 years ago in reply to Brandon.ConnectIQ

    Just a prompt to any user not providing an email address would be useful, saying something like: "are you sure you don't want to provide an email address because you won't be able to receive any reply".

     Mostly it's a problem when someone is asking you for help, but you can't reply or even tell them you can't reply. And they will probably think you are ignoring them ...