Alex Russell of Google/Chrome has published an essay arguing that Apple's control over iOS browsing does measurable harm to the web platform. His thesis is that Safari and WebKit are uniquely underpowered: repeated delays in shipping important features mean the web can never present a credible alternative to Apple's proprietary tools and App Store.
The argument credits Apple where credit is due, assigns blame fairly, and backs a complicated discussion with data. Read end to end, it points at three changes that would leave the web better off:
- Allow alternative browsers on iOS.
- Allow web apps in the App Store.
- Move faster on web platform features in Safari.
Considering the three asks
Each is easy to want in the abstract and harder to deliver in practice.
Alternative browsers
It seems reasonable that an expensive, powerful phone should run whichever browser its owner prefers, especially when the browser's maker is eager to ship it. The obstacles are likely well beyond outside understanding. One cautionary memory is a Chrome update that broke macOS outright; whether that kind of damage could visit iOS is unclear. A missing feature makes for unhappy customers in the abstract, but a bricked phone makes for very unhappy ones. The dynamic underneath may be simpler: Google, an advertising company, innovates on tracking technology, while Apple, a hardware company, innovates on privacy. The browser situation is one consequence of that standoff.
Web apps in the App Store
A web-app door into the App Store would open things up for developers who don't write native code — a large group. The complications again run past what an outsider can assess: quality control presumably gets harder, security presumably gets harder to lock down, and it isn't clear customers are asking loudly. Choice also exists at the platform level, since iOS holds only 15% of the phone market; anyone who wants a different browser and a different app store can have one.
Faster feature delivery
Every small Safari ship is worth celebrating; nobody wants to wait years for clearly useful capabilities. contain and container queries are the ones to watch on timing, because they matter for real work as soon as they stabilize without polyfills. The "Safari is the new IE" joke doesn't match day-to-day experience for typical web development: extremely capable sites ship to every browser, Safari included, without much fear of a second-class experience — gaming and VR/AR aside. Firefox draws more worry, since Mozilla faces the same web-feature onslaught with far less money than Apple or Google, though it currently seems to be doing fine.
The pace question
In practice, Safari's DevTools lag matters more than its platform features. There is a fair Apple-is-restrictive angle, and also an Apple-is-slow angle — but slow is relative. Slow compared to Chrome. Which raises a further question: why should Chrome dictate the exact speed of the web?
There is value in slower, more deliberate work: checking instincts, prioritizing design, and validating hypotheses before taking on technical debt. Iterating just enough before a release tends to produce better products, because once an API ships it can't be retracted or changed substantially. A slower-moving web can be frustrating, but it may also end up a better one. The right pace probably sits somewhere in the middle.



