On iOS, every browser you can install is a skin over WebKit, the engine inside Safari. Apps carrying Chrome or Firefox branding do not change what renders the page. The App Store Review Guidelines enclose this rule, and they're the reason the engine's identity matters more than the brand here: all three major browser vendors do have distinct engines (as of now), but on this platform only one is permitted.
Why it matters beyond principle
Restricting engines isn't just about the philosophy of gatekeeping. It comes with costs on both sides of the argument.
Security and the missing alternative
As Alex Russell writes, this isn't hypothetical: "none of this is theoretical; needing to re-develop features through a straw, using less-secure, more poorly tested and analyzed mechanisms, has led to serious security issues in alternative iOS browsers." He goes further, saying Apple's policy is "a veritable bug farm for the projects wrenched between the impoverished feature set of Apple's WebKit and the features they can securely deliver with high fidelity on every other platform," a serious blow to Apple's own justification for owning updates to iOS browser engines.
Alternative... to what, exactly?
Stuart Langridge points out the limits are tighter still: "Alternative browsers on iOS aren't just restricted to WebKit, they're restricted to the version of WebKit which is in the current version of Safari. Not even different or more modern versions of WebKit itself are allowed." And the result for users trying to leave Safari? "If they choose a different browser, they still get the same one. If there's a requirement from people for something, the market can't provide it because competition is not permitted."
PWA push notifications force an app install
Reporting to the UK Competition and Markets Authority, Bruce Lawson noted that the push notification gap matters: sites like Echo Pharmacy "have to build an app for iOS just because they want to send push notifications." The result is an odd trade against Apple's security and privacy rationale, since installing the app grants access to health and fitness data, contacts, sensitive identifiers, financial info, user content, user data and diagnostics, while a PWA with push would leak none of it. His conclusion: "I cannot recommend a PWA as being an equal experience on iOS simply here because of push notifications," and beyond current business, "it's also holding back future business."
What the two engines optimise for
Niels Leenheer argues the Safari and Chrome teams both work toward a safer, better web, but disagree on what the web should be. Google's aim: "improving the web by making it more capable," extending what it can do and competing with native apps.
Safari seems to focus on improving the web as it currently is. To let it be a safer place, much faster and more beautiful. And if you want something more, you can use an app for that.
The competing incentives that make that disagreement interesting are what a monopoly removes: since WebKit faces zero competition on iOS because Apple forbids it, the pressure to improve Safari is much weaker than it should be.
The gatekeeping argument cuts both ways
There's nuance worth acknowledging. On Mac, Apple restricts which OS you can install only through a sanctioned route such as Boot Camp. And plenty of iOS gatekeeping is desirable: when downloading simple games for a kid, one can hit upsells, ads and dark patterns galore, which warrants wanting Apple to block that garbage outright. That is asking for more gatekeeping and less simultaneously.
The difference with browsers is that users get no recurrence to opt out, unlike a service such as Google AMP, which you can avoid on your own sites and redirect away from elsewhere. This choice is made for you.
What the critics are asking Apple to address
Defences of Apple's restriction are scarce: mostly vague "Google can't be trusted" sentiment, framed around privacy, performance, or both. By and large, only Apple wants this lack of choice. As far as outsiders can tell, Apple hasn't stated clearly why the requirement exists, and having that would make it easier to address whatever the stated reasons cover.



