Answer every App Store review without it taking your morning.

Reviews are a channel, not a chore

A public reply is read by everyone deciding whether to download your app, not only by the person who wrote the review. An answered one-star review with a fix in it says more about your app than the star count does. Reviews also tell you what to build and which words your customers use, and that language is often better than what is in your listing.

If you run an app alone, reviews still tend to wait until you have an hour. Apptiller makes each one take a moment.

How it works

• New reviews are read every day with your App Store Connect key
• A model labels each with a short theme and a kind: bug, request, price complaint, praise or other
• Unanswered reviews appear in To review, with a drafted reply
• You edit it and send it, or skip it
• A reply you sent can be taken back

Themes, so the counts add up

The same complaint gets written twenty different ways. Apptiller labels new reviews against the themes it has already used, so you see one line saying seven people found recipe search slow, rather than seven separate reviews. No keyword lists are involved: a model reads the text, so sarcasm and other languages don't break the count.

Those themes then feed your listing drafts. What people praise tends to be what the next person wants to hear in your subtitle.

Your rating pace, by version

Star averages barely move once you have a few hundred ratings. Apptiller tracks something more useful: new ratings per 1,000 first-time downloads, now against the 28 days before and by app version. If a release made people stop rating, or a prompt you added started working, it shows up here.

A person is always the sender

Nothing is posted to the App Store without you. Drafted replies sit in To review until you act, and you can rewrite every word. That is a deliberate choice, because a wrong reply under your name is public and hard to forget. Apptiller does not post on autopilot, and does not ask for, buy or write reviews.

What makes a good reply

The best replies are short and specific. Thank the person for the detail, say what you are doing about it, and tell them what to do next. If a bug is fixed, name the version. If a request is planned, say so, and if it isn't, say that honestly too. Apple notifies the reviewer when you reply, and they can change their rating, so a clear answer to a fair complaint is one of the few ways to turn a one-star review around.

Avoid copying the same line under every review. Readers notice, and it suggests nobody read what they wrote. Apptiller's drafts start from what the review actually says, and you can make them sound like you before anything is sent.

A worked example

A reviewer gives two stars: "Love the plans but search takes forever." Apptiller labels it as a bug under the theme "Recipe search is slow", where six others already sit. The draft thanks them, mentions the fix in your next version and invites them to write to you. You change one word and send it.

Meanwhile the theme count tells you this is worth fixing first, and once the release is out you can see whether that theme stops growing. That single loop, from complaint to fix to a reply people can read, does more for your rating than any prompt.

What reviews teach your listing

Pay attention to the words people use when they praise you. If reviews keep saying "finally a meal plan that works with PCOS", that phrase is telling you who your best customers are and what they searched for. Apptiller feeds those themes into its listing drafts, so your subtitle can speak the way your customers do. It works the other way as well: a repeated complaint about price is a sign your page sets the wrong expectation.

Getting started

Connect an App Store Connect key with the App Manager role, and on Solo or above Apptiller reads your reviews each morning. Your first drafts appear in To review, under Review replies. Older unanswered reviews are worth a pass too, starting with the ones that people still see first.

Questions