App review management for indie developers

The four jobs

• Collecting. Reviews arrive in two places: App Store Connect and Play Console. Each store splits them further by platform or by country.
• Replying. One public reply per review, written for the reviewer and for everyone who reads the listing after them.
• Spotting patterns. Five reviews about the same crash after a release tell you more than a change in the average rating.
• Alerting. Finding out within a day that a release started a wave of one-star reviews.

At small scale, replying matters most

Both stores tell the reviewer when you answer. Apple says that when you respond, the reviewer is notified and has the option to update their review. Google says the user receives a push notification and an email after you reply, and Play Console tracks the ratings that changed after a reply.

A reply is the one part of review management that can change a rating you already have. A one-star review about a bug you fixed last week stays one star until someone tells the reviewer the fix is out. Dashboards and sentiment charts help you decide what to build next, but with 50 to 500 reviews a month you can read them all yourself.

Four ways to do it

1. The store consoles, by hand

Free and official. Fine for a few reviews a week in a language you write. The cost is the round trip: two consoles to check, the 350-character limit on Google Play to watch, and reviews in languages you can’t write that wait longest. The App Store and Google Play guides walk through each console.

2. A review analytics platform

These tools track ratings, keywords and competitors across many apps and many storefronts, usually with reply features built in. They suit product and support teams. Before signing up as a solo developer, check whether the plan with the reply features you need fits a one-person budget.

3. Your own script on the store APIs

Both stores expose reviews and replies through an API. A small script that fetches new reviews and posts replies is a reasonable weekend project for one app. Google only lists reviews from the last seven days, so the script has to run at least weekly. The reviews API guide covers authentication, limits and what to handle.

4. A tool built for replying

That is what I built Replylo to be. It brings App Store and Google Play reviews into one queue, drafts each reply in the reviewer’s language using the reply style you set, and posts only what you approve, from the web or your phone. It does not support multi-user teams, helpdesk integrations or posting replies without your approval. If you need those, one of the platforms above is a better fit.

A routine for 50 to 500 reviews a month

Every day or two

• Answer one- and two-star reviews that report a problem first. Name the problem, say what you know, give one next step.
• Reply in the reviewer’s language. A German review answered in English reads like a form letter.
• Skip asking for a better rating. Google’s reply guidelines ask for replies that address the comment, and a fixed problem earns the update on its own.

Every week

• Write down the three complaints you saw most. That list is your review analytics at this scale.
• When a fix ships, edit your reply on the reviews that reported it and name the version. Both stores let you edit a reply at any time.
• After each release, read the new reviews before the weekend, while the people who wrote them are still around.

What to measure

• Reply rate: the share of written reviews with a reply.
• Time to reply: days from review to reply. A reply a month later rarely gets read.
• Unanswered by language: if the backlog is mostly in languages you don’t write, that is the bottleneck to fix.
• Updated ratings: Play Console reports ratings changed after a reply, and App Store Connect can email you when a reviewer edits a review you answered.

If you want to try the reply-first approach, the support page explains how to connect each store.