Apple says it will let developers respond to reviews in App Store and Mac App Store when iOS 10.3 and macOS Sierra 10.12.4 ship
Context & Ripple Effects
This lands on the same day Apple announced it will cap review prompts at three per year in iOS 10.3, so the company is moving on both sides of the review pipeline at once: fewer interruptions for users, more accountability for developers. The change also answers a long-running developer grievance — MacStories argued back in 2015 that beta-period reviews were unfairly punishing apps and that Apple should filter them.
The response feature turns the App Store from a one-way ratings board into a public dialogue, and it set up what came next: Apple later added the ability to sort reviews by most helpful, most critical, or most recent in iOS 11.3, extending the same reworking of how reviews surface.
First-order effects
- Developers shipping on iOS 10.3 and macOS Sierra 10.12.4 gain a public reply channel for the first time, letting them answer complaints, correct misunderstandings, and post fixes directly under a review.
- Users reading an app's page now see whether a developer engages with criticism, making responsiveness itself a visible signal in purchase decisions.
Second-order effects
- Paired with the three-prompts-per-year cap, review volume gets scarcer and each review weighs more, pushing developers to invest in support and release quality rather than prompt-driven rating harvests.
- App pages become de facto customer-support surfaces, shifting some of the burden of complaint handling from private channels onto the storefront where rivals and prospective buyers can read it.
Third-order effects
- If the pattern holds — responses, prompt caps, then sorted and filtered reviews — Apple is consolidating the App Store as a curated reputation system it controls end to end, with developers' public conduct becoming part of what the platform ranks and surfaces.
The trend: Apple is steadily converting the App Store from a passive ratings board into a managed feedback ecosystem where it sets both how often users are asked and how developers answer.