The First Test: Does Choice Survive the Journey?
The App Store’s gateway position, the developer’s customer relationship, and the design of an external purchase route now point to one practical question: does choice survive the journey from discovery to support? This checkpoint connects those established ideas into a diagnostic for Apple’s proposed steering remedy. It gives readers a way to judge whether a change would alter the underlying dependence, rather than merely replace an explicit prohibition with a less visible barrier.
The test is deliberately demanding because a digital transaction is a chain. A developer needs to reach the user and communicate an offer. The user needs to compare options and complete one. Someone must handle payment, billing, refunds, and support. Apple must be able to address genuine risks without using safety or design control to suppress a legitimate alternative. If any link fails, the external route may exist in law while remaining weak in the market.
Dependence is a chain, not a pile of rules
It is useful to distinguish a list of restrictions from a system of dependence. A list says that Apple controls distribution, limits outside communication, requires IAP for many digital transactions, and manages parts of the post-purchase relationship. A system explanation asks how those controls interact.
Distribution gives the App Store its leverage. Developers of digital content and services may need Apple’s platform to reach a large and distinct user base. That makes the App Store difficult to treat as an optional shop, even when a developer has a website or a payment provider elsewhere. The user’s existing connection to the app and device ecosystem helps sustain the value of the gateway.
Communication then protects the route from comparison. If a developer cannot put a button, link, or information inside the app directing a user to an outside offer, the user may never learn that another price or payment arrangement exists. The restriction acts before the checkout screen. It limits not only where the transaction occurs, but which alternatives can enter the user’s field of view.
Payment control reinforces that communication barrier. If the developer must use Apple’s IAP system for digital goods and services, an outside processor cannot compete simply by offering a different price, support arrangement, or technical service. A merchant-of-record service cannot take on the sale where Apple reserves that role. The developer’s ability to design the commercial relationship is narrowed at the same time as the customer’s ability to compare it.
The post-purchase relationship completes the loop. The CMA records developer concerns about limited access to customer information, control over refunds, and the ability to provide direct support. A developer may still bear reputational responsibility for a product while having less control over the transaction that produced the complaint. The loss is therefore not merely a fee paid at checkout. It is a weaker feedback connection between the business and the customer.
That feedback connection affects future choices. Less information can make it harder to understand who is buying, tailor offers, coordinate support across platforms, or improve a service. Less margin can reduce the money available for features, new products, or expansion. A rival to an Apple first-party app may also have less room to compete if it pays a commission and cannot offer a different route to users. These effects are reported concerns supported in part by confidential or redacted submissions, so they should not be treated as a measured result for every developer. The mechanism is nevertheless coherent: control over access, communication, payment, and feedback can compound rather than merely add.
The physical-goods boundary helps sharpen the point.