Reply Rules for Every App Store: Character Limits, APIs, and Notifications

You can reply to reviews on most major app stores — Apple, Google Play, Samsung, Huawei, and Microsoft all let a developer respond — but the mechanism, the character limit, the API, and what the reviewer sees on the other end change with every single one. Amazon is the exception: it retired developer replies entirely in December 2020, so on the Amazon Appstore you can read reviews but not answer them.

There's no single table on the web that lays this out honestly, so here it is. Below is every store where reviews live, how you actually post a reply, the character cap (documented or not), whether there's a real API to automate it, and whether the person who wrote the review ever finds out you responded. If you ship one app across several storefronts, this is the cheat sheet for knowing where a reply is even possible before you waste an afternoon hunting for a button that doesn't exist.

Start with the short answer, store by store. Each line below is one row of the reference: where the reply gets typed, the character limit, whether an API exists, and the notification behavior. The stores that matter most for reach, Apple and Google, sit at the top; the rest trail off into portals you'll rarely open.

The two stores you'll reply to most have the widest gap in constraint. Google Play is the strict one: 350 characters, hard-capped, counted with spaces and punctuation. That's less than this paragraph. It forces a discipline — acknowledge, give the fix, one next step — that turns out to make replies better, not worse. When researchers ranked what makes a developer response likely to move a rating, the top predictor was the length ratio between the review and the reply, not politeness or speed (Srisopha et al., EASE 2021). A tight response proportional to the complaint beats a padded one.

Apple is the loose one, and also the unsettled one. Apple publishes no official character limit for App Store responses; community testing has floated numbers in the low thousands (one figure often cited is ~5,970, another ~10,240), but Apple states none, so don't design against a hard number that isn't documented. Practically, if you write a single reply meant to fit both stores, size it for Google Play's 350 — it's the tighter, real constraint. Microsoft Edge Add-ons sits in the middle at a clean, documented 1–1,000.

This is the line that separates 'you can automate replies' from 'someone lives in a dashboard.' Three stores expose a working, documented API you can post a reply through: Apple's App Store Connect API, Google's Play Developer API, and Huawei's AppGallery Connect Comments API. The shape is similar across the first two — authenticate, target a review by id, POST the response text.

The other stores are portal-bound. Samsung's replies happen in Seller Portal with a bulk-select helper, but there's no widely documented public reply endpoint. Microsoft's Store Services API technically has a review-response method, yet Microsoft steers you to Partner Center because it's been flaky, and the Edge Add-ons reviews API is openly described as not in a working state. So in practice: Apple, Google, and Huawei can be driven by machine; Samsung and Microsoft mean a person in a browser tab; Amazon means nothing at all. If you're evaluating an aggregator that claims 'reply from one dashboard' across all of these, ask specifically which stores it *publishes* to versus which it only *monitors* — the honest ones, like [AppFollow](/vs/appfollow), are clear about the split.

The notification behavior is the part most teams never check, and it changes how much a reply is worth. On the App Store, Apple notifies the reviewer when you respond and gives them a one-tap path to update their review, which is the whole mechanism behind the 'replying raises ratings' effect. On Google Play, the reviewer receives an email containing your reply, so even a public-facing response lands in a private inbox. Huawei is the odd one: your reply only goes public after the comment itself is approved, so there can be a lag before anyone sees it.

That notification loop is why replying is worth the effort at all. When Google introduced recency-weighted ratings at I/O 2019, it reported that responding to reviews correlates with an average lift of 0.7 stars. Academic work backs the direction: across 4.5 million reviews, users who got a response were roughly six times more likely to raise their rating than those who didn't (4.4% vs 0.7%, Hassan et al.). The reply doesn't just answer one person — it nudges a notified reviewer back toward the store, and it reassures the next hundred people reading before they install. We unpack that causal chain in [does replying to app reviews raise your rating](/blog/does-replying-to-app-reviews-raise-your-rating), and if the harder problem is simply *hearing* about new reviews fast enough to reply, that alerting layer (Slack, Telegram, email) lives in [our integrations](/integrations).

That reply runs under 180 characters, comfortably inside Google Play's 350, and it would post unchanged on Apple, Samsung, or Edge Add-ons too. Design to the tightest documented cap and one reply travels across every store that accepts one. The store-by-store differences, including this exact character gap, get the full treatment in [App Store vs Google Play review replies](/blog/app-store-vs-google-play-review-replies).

Be honest about reach. For most apps, Apple and Google are where the reviews — and the ratings that drive installs — actually accumulate, and they're the two stores with reliable reply APIs and reviewer notification loops. That's exactly where ReplyArgus publishes: Apple App Store and Google Play, in one inbox, in 100+ languages. We're deliberately clear that we don't publish to Samsung, Huawei, Microsoft, or Amazon — nobody credibly auto-publishes to Amazon, because Amazon killed the feature. If those secondary stores carry real volume for you, budget a monthly pass through each portal by hand; automate Apple and Google first, and treat Samsung or Huawei as a cleanup rather than a daily fire.

That's the whole map: eight storefronts, three real APIs, one hard character cap, and one store that quietly took the feature away. Keep the reference handy, automate the two stores where reach and APIs both live, and give the long tail a scheduled manual pass. [Start free with ReplyArgus](/signup), no card required, and Argus drafts your first Apple and Google Play replies in minutes, each one sized to the store's limit and written in the reviewer's own language.