How Long Until Your Developer Reply Appears? (Apple vs Google)

A developer reply usually appears on Google Play within minutes, but on the Apple App Store it can take up to 24 hours to go public. Apple holds every response in a Pending state first. That gap isn't a bug on your end and it isn't a slow tool. It's simply how the two stores publish responses, and no service, script, or app can make Apple's clock run faster.

So if you replied an hour ago and it's live on Play but still nowhere to be seen on the App Store, nothing is broken. Below is the exact timing for each store, why iOS lags, what "pending" actually means, and the short list of things that mean your reply is genuinely stuck rather than just waiting its turn.

The honest answer depends entirely on which store you're replying in, because the two publish responses in completely different ways:

Google Play treats a developer reply almost like any other content update: you submit it, it goes into the queue, and it's live shortly after. Fast, near-real-time, done. Apple takes the opposite posture — every response is held and reviewed before it goes public, which is why App Store Connect shows it as Pending in the meantime. Apple doesn't publish the specifics of what happens during that window, only that it "may take up to 24 hours."

Practically, the two stores need different mental models. On Play you reply and can screenshot the live response minutes later. On the App Store you reply and then wait. The response is committed, but it won't be visible to the public until it clears. If you manage both stores side by side, that split is worth internalizing; we break down every difference in [App Store vs Google Play review replies](/blog/app-store-vs-google-play-review-replies).

Pending is the normal, expected state for a reply you just submitted — not an error. Apple's documentation spells it out directly:

A couple of things follow. Only one response per review ever appears, so you can't stack replies, and if you edit a response Apple adds a small notation showing it was edited. None of that changes the headline: if it's under 24 hours old and marked Pending, you're just waiting.

Most ["my reply isn't showing"](/blog/developer-reply-not-showing) moments resolve themselves inside the normal window. Here's the short list of cases that are genuinely worth a second look:

It matters more than the raw "is it visible yet" question suggests, because the value of a reply decays with time. Google shared at I/O 2019 that apps see roughly a +0.7-star average lift when developers respond to reviews, and that ratings became recency-weighted that same year — so a fresh one-star answered fast counts for more than an old rating ever will. Srisopha et al. (EASE 2021) found timeliness among the top predictors of a reply that wins a reviewer back, ahead of politeness. The clock that matters isn't Apple's 24-hour publish window; it's how long the review sat before you answered it. We dig into that in [review velocity](/blog/review-velocity).

Here's the catch nobody advertises: the publish delay is fixed by the store, but the *reply* delay is entirely on you. If a Portuguese one-star lands Friday night and nobody drafts a response until Monday, you've burned three days before Apple's 24-hour clock even starts. That backlog, not the platform, is what usually makes replies feel slow. Closing it is what [ReplyArgus](/features) is built for: it watches your Apple App Store and Google Play reviews in one inbox, drafts an on-brand reply in the reviewer's own language the moment a review lands, and lets you approve and publish it straight to the store's API — so the countdown begins as early as it possibly can, on both stores, without you living in two consoles.

That reply works because it's fast, specific, and grounded: it names the fix and owns the delay instead of hiding it. A tool can't make Apple's publish window shorter, but it can make sure a draft like that is ready to approve in seconds instead of sitting in a queue for a week. For teams that want the whole loop to run from where they already work, there's an [MCP connector](/agentic-tools) so you can draft and hold replies from Claude, ChatGPT, or Cursor.

The timing itself is out of your hands: Play in minutes, the App Store within a day. What you control is everything before the submit button, namely how fast you see the review and how fast a good reply is ready to ship. If you'd rather not babysit two consoles waiting on Pending states, [start free with ReplyArgus](/signup) (no card) and Argus will watch both stores, draft a reply in the reviewer's language the second a review lands, then get it approved and submitted so the store's clock starts the moment it can.