Replying to store reviews: the public support desk you already have
Play holds new reviews roughly 24 hours but lets you reply immediately; Apple allows one editable public response per review. A triage-and-close-the-loop playbook that earns updated ratings.
Reviews are the only storefront your users write for you. A thoughtful reply turns a one-star bug report into a support ticket you can fix, and future shoppers read the developer's responses as much as the reviews. Both stores let you reply publicly, and both wrap replies in mechanics worth knowing before you type the first one.
How Google Play handles it
On Google Play, new reviews are generally held back for around 24 hours before going public while Google screens for suspicious activity - but you can see and reply to them during that window. That is an operational gift: you can resolve a problem and have the reply waiting when the review goes live, before the complaint has an audience. Play Console also shows updated ratings over time, so you can see when a user revises a review after a fix - which is the entire point of replying well.
How the App Store handles it
App Store Connect lets you publicly respond to a review, and only one response per review appears on your product page; you can edit or delete it later, and edited responses carry a notation. Responses may take up to 24 hours to appear and sit as pending in App Store Connect until then - write them to age well. As on Play, the response is public and attached to the review for every future visitor, which makes tone a business decision, not a mood.
The reply playbook
- Triage by impact, not anger. Crashes, data loss, payment problems and anything mentioning security get same-day replies. Feature requests and taste disagreements can wait for a batch.
- Acknowledge, state the fix or the path, stop. "You're right - the export bug in 3.2 corrupted filenames; 3.2.1 is out now and repairs them on first open" beats three paragraphs of apology. Specifics signal a real team; templates signal a mailbox.
- Never argue, never blame. The reply is written for the hundred future readers, not the one reviewer. A reviewer who is factually wrong still gets a courteous correction.
- Take identity and details off the public thread. Ask for the order number or device logs through your support channel, never in the public reply - and never post a user's account details back to them.
- Close the loop. When the fix ships, a short follow-up reply ("fixed in 3.2.1") is what earns the updated rating both stores surface.
Feed reviews back into the product
Reviews are a free, continuous usability study. Tag incoming reviews by theme (crash, pricing, missing feature, UX confusion) and let the monthly count steer backlog priorities; a theme that triples after a release is a regression report with better distribution than your telemetry. Both consoles offer filters and exports for exactly this. And resist the dark patterns: no incentivised positive reviews, no staff reviews, no reply farms - both stores police all three, and the penalty costs more than any rating bump earns.
Where to start
Reply to every review from the last 30 days that mentions a real problem, tag the themes, and set a standing twice-weekly triage slot. Within a month you will have a public record of responsiveness - the quietest, cheapest trust signal on your store page.
Sources
- Google Play Console Help: View and analyze your app's ratings and reviews
- Apple: Responding to reviews
Prepared with AI assistance and reviewed before publication. Play's ~24-hour review hold and updated-ratings features are paraphrased from Google's Play Console Help checked on 19 November 2026; App Store response mechanics from Apple's documentation.
Next step: Compare real product starting points in the Omnistu services catalogue, or email team@omnistu.com with your requirements for a written scope.