Since the Mountain View company decided to change Android Market to name it Google Play, we've seen a large number of changes and improvements, both in design and functionality. However, there was still one problem for which a solution had not been provided. Users were leaving comments on the different applications, some praising them, others harshly criticizing them, and a third type requesting technical help or who asked questions of the developers. However, these questions couldn't be answered—until now.
This problem has already been fixed. We do not know if it was a problem or if Google decided from the beginning that users should have complete freedom when writing their comments, without any developer being able to influence people's opinions or cause controversy among the comments. The idea was that they would serve as a real reference for users looking for guidance on a certain application.
However, this left a clear problem. If it was the only, or at least the fastest, means of communication to reach the developers of that particular application, this would prevent the developers from being able to respond to technical queries that users will make. Therefore, it's normal to find the address where we can contact the developers within the application description, so that users can quickly find it.
However, Google has decided to make changes in this regard, at least as regards the top developers de Google PlayFrom now on, users will be able to respond directly to user comments, so they can resolve any questions they may have. This will be a good solution, for example, for all those users who have very basic problems with their application, perhaps because they don't know how to configure its startup, or because they don't fully understand how it works. Any user reading the comments looking for opinions about the application would not be impressed by a negative comment, when it may be completely wrong. The ability to respond will allow developers to to clear doubts, both for the person asking and the person encountering them. This option is now widely available, so more teams can manage conversations with their users from the app's own listing.
Why direct response improves the experience
Allowing the developer to respond on the app listing provides immediate context: corrects misunderstandings, announces arrangements and guides anyone who comes with the same question. This way, a negative comment about an already resolved error does not unfairly influence the download decision and a continuous improvement cycle in the app.
In addition, public conversation raises the quality of reviewsWhen the team addresses criticism clearly and respectfully, users often refine their assessment, and many update their rating after a correction.
How to contact the developer and what to include
On Google Play, the developer is responsible for supporting their app. contact the developer if any of these situations occur:
- An application not working or closes unexpectedly.
- An in-app purchase or subscription It has not been delivered, it does not work or it is not what was expected.
- You want a reimbursement and the direct option was not available.
- There are problems to recover progress or save files.
- Do you want to Get more info on the use of a function.
To speed up resolution, always provide: app name, description of the problem (steps, error messages, device and version) and the type of response that you expect (help, replacement, refund). In incidents with purchases, a professional and appropriate response is expected in a short term of working days.
After contacting, you can write a public review Commenting on your support experience. This guides other users and gives visibility to the teams that provide prompt support.
How public answers work on Google Play
The developer's answers are public in the app's page. The user who commented receives a notification When the team first responds to that review; if the developer updates their response without the user editing their review, they are not notified again. When the user edits their comment, a new share may generate another notification.
Good practices: answers clear and relevant, friendly tone, no sensitive data, no self-promotion, and solution-oriented. Google considers this capability a privilege; Abuse or non-compliance may result in account limitations or removal of the feature.
Reply to Reviews API: Integrate support into your workflow
The Google Play API Reply to Reviews allows you to view and respond to reviews from your CRM or support tool. It only exposes production reviews that include text; ratings without comments are not available in the API.
Access and Permissions: Authorize with OAuth or service account with permission Respond to reviews. You can list recent reviews or retrieve a specific review, translate its content with the parameter translationLanguage, and reply with a limit of 350 characters en replyTextAvoid generic automations: customize templates and make the next step clear.
Notifications and fees: the user receives notice with the first answer after your comment. The API applies per-app limits (e.g., hourly queries and daily responses), which can be extended upon request. Never include sensitive information in the public response.
Testing on Play Console before going into production
To ensure quality, Play Console drives a flow of stepped tests:
- Internal testing: rapid distribution to a small, trusted group.
- Closed tests: A larger group managed by the developer to polish bugs and validate policies. It is required to perform at least one closed test with a minimum of 12 testers active during 14 consecutive days to request access to production.
- Open tests: Anyone can join and post private comments once the listing is ready.
- Manufacturing: general release when preparation is accredited.
During testing, feedback is Private and are consulted in the Play Console, with filters by language, version, and device. Incorporating diverse and representative testers helps detect issues usability and compatibility before launch. Upon meeting the requirements, you'll request production access by answering questions about the test, the app, and its preparation.
Good practices to improve the quality of reviews
– Publish a section of visible support in the tab (email and help site).
– Respond with speed to critical purchases and failures; documents recurring solutions.
– Use short templates for typical cases, but customize each answer.
– Invite to update the review when the problem remains resolved (without undue incentives).
– Prioritize improvements based on the standards of comments and stability metrics.
Google Play becomes an effective channel for assistance and bidirectional learning: Users receive contextual help and developers gain actionable insights to iterate their apps faster, reducing friction and steadily improving ratings.
