Mac App Store Reviews: A Developer's Guide to the Forgotten Surface

Your Mac app almost certainly has a fraction of the reviews your iOS app does, and each one carries more weight. Mac App Store reviews come from a smaller, more technical audience (people who chose to buy through the store instead of grabbing a notarized build off your site), and they tend to tell you exactly what's broken. The catch is that Apple tucks them behind a platform toggle most developers never click, so a whole channel of sharp feedback sits unread and unanswered.

Here's the short version: Mac App Store reviews live in the same App Store Connect you already use for iOS, under the same Ratings and Reviews tab — you just switch the platform selector from iOS to macOS. The reply flow is identical (find the review, click Respond, submit, wait for moderation), and the reviewer gets the same notification with a one-tap route back to raise their rating. Below: where they actually live, why the low volume is a feature not a bug, and how the reply mechanics differ just enough to catch you out.

In the exact same place as your iOS reviews, which is why they're so easy to miss. When an app ships on more than one platform, App Store Connect doesn't merge the reviews — it separates them by platform and shows one at a time. The Ratings and Reviews page defaults to whatever platform loads first (usually iOS), and there's a platform picker at the top. Flip it to macOS and a different, usually much shorter list appears.

That separation goes deeper than the list view. A Mac app carries its own star rating, distinct from the iOS rating, even when the two are sold as a single universal purchase. Reviews are still per-storefront too: a review on the U.S. Mac App Store is a separate object from one on the German Mac App Store. So the real map is three-dimensional: platform, then territory, then version. For the full breakdown of what's per-platform, per-region, and per-build, see the [app review reply mechanics reference](/blog/app-review-reply-mechanics-reference).

The Mac install base is smaller than iOS, plenty of Mac software ships outside the store entirely, and desktop users are simply less prompted to rate than someone tapping through a phone app. Add it up and most Mac apps see review counts that would look like a rounding error next to their iOS numbers. That's not a reason to ignore the channel — it's the reason to treat it as premium.

The people who do leave a Mac review skew toward a particular profile, and it changes what the feedback is worth:

That last point is the whole business case for replying at all. Google's I/O 2019 data showed developers who respond to reviews see roughly a +0.7-star average lift over time, and Hassan et al.'s study of 4.5 million reviews found users who got a developer response were about 6 times more likely to raise their rating than those who didn't (roughly 4.4% versus 0.7%). On a Mac listing where every rating is load-bearing, that leverage is amplified, not diluted.

Mostly yes, with two catches. The reply box, the moderation delay, the one-response-per-review rule, and the reviewer notification loop all behave identically to iOS — if you've replied to an App Store review before, you already know the flow. The step-by-step is the same one we cover in [how to reply to reviews in App Store Connect](/blog/how-to-reply-to-reviews-in-app-store-connect); it just runs after you've flipped the platform to macOS.

The two catches: first, you must be on the macOS view to see and answer Mac reviews. Reply to the iOS list all day and the Mac queue stays untouched. Second, the same role gating applies. Responding is generally limited to the Account Holder, Admin, App Manager, and the dedicated Customer Support role. If a teammate owns review replies, give them Customer Support (least privilege, same reply box) rather than Admin. Here's what a reply that earns the edit looks like on a Mac-specific complaint — it names the exact behavior and makes a keepable promise:

There's no separate Mac limit — it's the same unsettled Apple ceiling as iOS. Apple publishes no official character count for developer responses on either platform. Community testing lands on wildly different numbers, some reporting a cap near 5,970 characters and others closer to 10,240, and Apple has confirmed neither. Treat it as 'plenty of room you shouldn't use': a two-sentence reply that names the bug beats a five-paragraph essay. (Google Play, by contrast, enforces a hard, published 350-character cap. The two platforms diverge in more places than this — we lay them side by side in [App Store vs Google Play review replies](/blog/app-store-vs-google-play-review-replies).)

The deeper trap isn't the limit — it's forgetting the Mac queue exists. Because it's one toggle away from the iOS list you check daily, weeks go by and a handful of fixable, rating-moving reviews sit unanswered. On a listing with a small rating count, that neglect is visible to every buyer comparing your Mac app to an alternative.

The manual answer is a calendar reminder: every Monday, open App Store Connect, flip to macOS, triage Most Critical, reply. That works right up until a busy week eats the reminder — and the small, out-of-sight Mac queue is exactly the surface you'll skip first.

That's the seam [ReplyArgus](/features) closes. It connects through App Store Connect, the same account that serves your Mac reviews, so a macOS app's reviews land in one inbox alongside your iOS and Google Play reviews, with no toggle to remember. Each new review drafts an on-brand reply grounded in your past approved answers and an auto-ingested knowledge base of your store listing, and a review in Japanese or Turkish comes back drafted in that language, both directions. Nothing publishes until you approve it, or until a rule you set does (by rating, keyword, language, or store). The high-signal Mac reviews stop being the ones that slip.