lundi 17 avril 2017

Google Adds the Ability to Report Reviews That Violate Their Comment Posting Policy to the Developer Console

Google is always adding to the Google Play Developer Console to enhance the UX for application developers. A little over a year ago Google added some very useful ratings and review tools to the platform. We went hands-on with the Developer Console last year so that developers and regular users alike could get an idea of how certain features work. People are still hoping to see Google add more features to it and right now they are beta testing one with a select number of developers.

Anyone can report an application review if it violates Google’s comment posting policy, but they don’t make it very accessible. For instance, you have to be using the Google Play mobile application to report an application review because the feature just isn’t available on the web portal. This isn’t really a big deal, but it is definitely something that seems missing. So until now, developers would have to load up the Google Play application, find their application or game and then hunt down the offending review.

So a new beta feature from Google hopes to solve that issue as they’re starting to let developer report reviews directly from the Developer Console. Google recommends all developers look over the Comment Posting Policy for Google Play so they are up to date on what is and is not allowed to be in a review. However, this new feature is not available to all developers right now. Google says they are testing this feature on “select developers” and they could disable it at any time.

At a later date, Google will decide if this feature produces good results or if it is being abused. If they feel the good outweighs the bad, and the service can scale properly, then they will roll it out to all developers. There’s no telling how long this beta testing period could take though, and there isn’t a way to manually enable it on your account.

Source: Developer Console Help



from xda-developers http://ift.tt/2pJ4hsW
via IFTTT

Aucun commentaire:

Enregistrer un commentaire