All posts
GuideJul 8, 2026 · 10 min

Can You Reply to Amazon Appstore Reviews? (2026)

No, you can't publicly reply to Amazon Appstore reviews. Amazon retired the developer-reply feature in 2020. Here's what to do with that feedback instead.

RA

The Argus Team

Reply Argus

No, you can't publicly reply to Amazon Appstore reviews. Amazon retired the developer reply-to-reviews feature back in December 2020, and it hasn't come back since. There is no button in the Amazon Developer Console, no API, no back door: a customer leaves a review on your Fire tablet or Fire TV listing and you simply cannot post a public response to it the way you can on the App Store or Google Play.

That surprises people, because a public reply feels like table stakes for an app store in 2026. But Amazon is the odd one out. If you landed here hoping for the steps to answer an angry Amazon reviewer, the honest answer is that there aren't any. What you can do is monitor that feedback, route it somewhere useful, and win the stores that do let you reply. Let's cover both.

The one-line version

Amazon removed developer replies from the Appstore in December 2020. You cannot post a public response to an Amazon Appstore review today. You can still read those reviews, act on them, and reply publicly on the two stores that support it — Apple App Store and Google Play.

Wait, Amazon really removed developer replies?

It did. For a while the Amazon Appstore let developers respond to customer reviews, but the feature was buried and barely used, so Amazon pulled it in December 2020. Because the reply box was never wired into the main Developer Console the way Apple's and Google's are, most developers never even knew it existed, and a feature nobody finds is a feature that gets cut.

Developers have been asking for it back on the Amazon developer forums ever since, pointing out that a public reply is standard on Google Play and the App Store and that it's strange to ship an app store without one. As of 2026, Amazon has not reinstated it. Treat public replies on Amazon as unavailable and plan around that, rather than waiting for a button that may never return.

So what can you actually do with an Amazon review?

Plenty, just not publicly. A review you can't answer is still a signal you can act on, and Amazon's audience (Fire tablets, Fire TV, Kindle devices) is a real slice of installs worth listening to. The moves that matter:

  • Read them in the Developer Console — reviews and star ratings still show up in your Amazon dashboard even though the reply box is gone. Check them the way you'd check any inbox, because they're the only unfiltered voice of your Fire-device users.
  • Route the complaint into your roadmap — a one-star that says 'crashes on Fire HD 10 after the update' is a bug report with a device name attached. That's more actionable than any reply you'd have posted. Cluster the recurring ones and fix them.
  • Answer through channels you do control — your in-app support, your support email, a pinned FAQ, a changelog. You can't reply on the listing, but you can reach the same user everywhere else and close the loop.
  • Let release notes do the talking — since you can't tell a reviewer 'fixed in 2.4.1,' put it in the update description. Users who left the complaint often read the notes when the update lands, and a shipped fix moves ratings even without a public reply.
  • Ask happy users to update their star — with no reply lever, the product and its release cadence are what nudge a rating back up. A visible bug-fix streak does the persuading that a comment would have.

Don't try to fake a reply

Some developers, cut off from replies, create a second account to post a 'response' as a fake user or plant a five-star rebuttal. Don't. That's review manipulation under Amazon's guidelines and it can get your listing pulled. If you can't reply honestly, don't reply at all — fix the thing and let the update speak.

Where you can reply: Apple App Store and Google Play

Here's the part worth your energy. Two of the three big stores do let you respond publicly, and those replies genuinely move numbers. Google reported at I/O 2019 that developers who respond to reviews see an average lift of about 0.7 stars. A study of over 4.5 million reviews by Hassan et al. found users were roughly six times more likely to raise their rating after a developer replied (4.4% versus 0.7% with no reply), and McIlroy et al. (IEEE, 2017) found that when a rating changed after a response, 38.7% of those changes were increases. None of that is available to you on Amazon. All of it is on Apple and Google.

The two stores don't play by the same rules, though. Google Play caps developer replies at a hard 350 characters and lets you edit or delete them freely; Apple publishes no official character limit (community testing suggests a few thousand characters) and notifies the reviewer when your reply posts. We mapped the full matrix in [reply rules for every app store](/blog/reply-rules-for-every-app-store), and broke the two head-to-head in [App Store vs Google Play review replies](/blog/app-store-vs-google-play-review-replies). If the review is a rough one, [how to respond to negative app reviews](/blog/how-to-respond-to-negative-app-reviews) has the playbook that earns the edit.

Loved this app on my phone but on the Fire tablet it keeps logging me out every time I close it. Frustrating.

Reply

Thanks for sticking with us across devices. That logout loop was a session-token bug specific to Fire OS, and the fix shipped in 2.4.1. Update and it should keep you signed in between opens. If it still drops you, email support@ and we'll pull your logs and sort it directly. Appreciate you flagging the exact device.

That reply names the device, the build, and the fix, and it's the kind of thing you'd post on Apple or Google in a heartbeat. On Amazon you can't, so the same message goes into your release notes and your support reply instead. The instinct is identical; only the surface changes.

How to handle Amazon feedback without a reply button

A repeatable loop beats reacting to each review one at a time. Here's the workflow that turns un-answerable Amazon reviews into shipped fixes.

  1. 1

    Step 1 — Pull the reviews

    Open the Amazon Developer Console and read the ratings and reviews for each app on a set cadence (weekly is plenty for most). Copy the recurring complaints and note the device model when it's mentioned.

  2. 2

    Step 2 — Cluster by theme

    Group the reviews into buckets: bug, missing feature, confusion, pricing gripe. A theme that shows up five times is a roadmap item; a one-off is a note.

  3. 3

    Step 3 — Fix and ship

    Route the bug clusters to engineering and prioritize the ones hitting the most users. Since you can't reply, the fix itself is your response.

  4. 4

    Step 4 — Answer in the update

    When the fix lands, spell it out in the release notes ('Fixed a logout loop on Fire OS'). Reviewers who complained often read the notes, and a named fix does the work a public reply would have.

  5. 5

    Step 5 — Reply where you can

    The same user, or a user with the same bug, is on Apple and Google too. Post the real public reply there, where it counts toward your rating and reaches the reviewer directly.

The through-line is that Amazon reviews aren't wasted just because you can't answer them; they're just a different kind of input. But steps 1 through 5 are a lot of manual reading and re-typing once you're on two live stores and a third you can only monitor, in more than one language, week after week. That's the point where doing it by hand quietly stops happening.

This is the slice [ReplyArgus](/features) owns. To be straight with you: it doesn't touch the Amazon Appstore, because no tool can publish a reply where the store offers no reply surface. What it does is take over the two stores that do let you respond. It watches your Apple App Store and Google Play reviews in one inbox and, for every written review, drafts a grounded, on-brand reply in the reviewer's own language (100+ supported, both directions), already sized to each store's limit. You approve in a click, or opt into rule-based auto-publish for the clean cases. It also clusters those reviews into a PM roadmap board you can export to Jira, Notion, or Google Sheets, which is the step-2-and-3 loop above done for you. The reviews you can reply to stop going cold, freeing your Amazon time for the one thing that lands there: reading and fixing.

The shortcut

You can't reply on Amazon, so don't burn hours pretending you can. Own the two stores that do support replies with ReplyArgus — every App Store and Google Play review gets a drafted reply in the reviewer's language, sized to each store's limit — and keep your Amazon time for the one thing that works there: reading the feedback and shipping the fix.

Frequently asked

Can you reply to Amazon Appstore reviews in 2026?
No. Amazon removed the developer reply-to-reviews feature in December 2020 and has not reinstated it. There's no reply button in the Amazon Developer Console and no API for it, so you cannot post a public response to an Amazon Appstore review today.
Why did Amazon remove developer replies?
The feature was poorly surfaced and rarely used. Because the reply box was never integrated into the main Developer Console the way Apple's and Google's reply tools are, few developers ever found it, and Amazon retired it in December 2020. Developers have asked for it back on the Amazon forums since, but it remains gone.
How do I respond to Amazon Appstore feedback if I can't reply?
Read the reviews in the Amazon Developer Console, cluster the recurring complaints, and fix the bugs they name. Then answer indirectly: spell out the fix in your update's release notes and reach the user through in-app support or your support email. You can't reply on the listing, but you can close the loop everywhere else.
Which app stores let developers reply to reviews?
Apple App Store and Google Play both support public developer replies. Google Play caps replies at 350 characters and lets you edit or delete them; Apple publishes no official limit (community testing suggests a few thousand characters) and notifies the reviewer when you respond. The Amazon Appstore does not support replies at all.
Does replying to reviews actually change ratings?
Yes, on the stores that allow it. Google reported at I/O 2019 that responding developers see an average lift of about 0.7 stars, and a 4.5-million-review study by Hassan et al. found users were roughly six times more likely to raise their rating after a reply (4.4% versus 0.7%). That upside is real on Apple and Google, and unavailable on Amazon.
Does ReplyArgus support the Amazon Appstore?
No. ReplyArgus watches and replies to the Apple App Store and Google Play only, because those are the stores that offer a reply surface. Since Amazon removed developer replies, there's nothing there to automate. ReplyArgus handles the two stores you can act on and drafts every reply in the reviewer's own language.

So the short answer holds: you can't reply to Amazon Appstore reviews, and no tool can change that until Amazon ships the feature again. What you can do is read that feedback, turn it into fixes, and reply for real on the stores that support it. [Start free with ReplyArgus](/signup) (no card) and Argus drafts your first App Store and Google Play reply in minutes, so the reviews you can answer never sit waiting while you're busy fixing the ones you can't.

Try it

Let Argus draft your next reply.

Watch it answer a real review in your voice. 10-day trial, no card to begin.

See the features or pricing.

Keep reading