For the non-geeks who accidentally see this post, the browser engines set the rules for what is possible, including new standards, plug-ins or other advancements to the web, and when they become available for your device. Not all browser engines advance at the same speed, but largely, the lead developers learn from one another and the web moves forward.
That only works when all players are working together, and move at the same speed. The UK's competition watchdog said more than a year ago that Apple was holding back innovation on mobile browsers. Alex Russell, who works on Edge at Microsoft, and previously at Google on Chrome and the web platform, has chronicled how browser choice on mobile matters a lot to users for years, and has long said "Apple's iOS browser (Safari) and engine (WebKit) are uniquely under-powered." Call him biased if you want, but he's right and not alone in this view.
This week, Mozilla brought this up again, talking about how "Apple forces all browsers on iOS to be built on Apple’s own browser engine," which is essentially like forcing everything to be a little bit broken. Firefox is a great alternative to Safari as much as Chrome is, depending on your preference, but if it's hobbled from the get go, user benefit is limited.
If you remember your Apple history, you remember how Steve Jobs was initially very much opposed to 3rd party apps on the iPhone, for fear they would cause harm to the device or the network. But the position was changed and the app store became a runaway success. In history echoing itself, Apple has set conditions for Mozilla and others (Google included) that force the browsers to go through a narrow approval process, theoretically for security reasons and user benefit. Mozilla writes that in the three years since the EU forced alternative browser engines that "not one developer has been able to launch a non-WebKit browser on iOS. The reason is simple: Apple’s conditions remain unworkable."
Not great!
Way back in 2008, I wrote that The New World of Browser Choices is All About the Hooks and argued that web surfers expect consistency, but gatekeepers often prioritize platform control over open standards. Ironically, I used a Safari logo on that post, but don't fault me for the snapshot of the time. In 2011, I talked about the very real platform friction users ran into as we tried to make our experiences aligned on desktop and mobile when approaches were very much fragmented. I'd posit that if you're fighting for the user and not trying to protect a moat with unqualified tech, you'd open up a bit more and try to stay at the forefront of innovation, but commercial realities sometimes get in the way.
User desire for open choice is not going away. Keeping the web honest requires conscious effort and robust maintenance, ensuring that vendors do not dictate the full limits of what software can achieve on our primary personal devices, or hold us back while others are innovating. Mozilla is right to call this out and we should always speak up when tech giants get in the way -- including my personal favorites.
Disclosures per always: I work at Google, which makes Chrome and Android. I don't explicitly work on those teams, but I have been a strong web platform advocate from the beginning and that continues. Nobody at Google reviews my blog posts.