· via Hacker News – Front Page (hnrss.org)
Mozilla says Apple's iOS rules still block non-WebKit browsers as Firefox use doubles in EU
Mozilla says no developer has shipped a non-WebKit browser on iOS nearly three years after Apple's DMA-driven conditions, even as EU choice screens have doubled Firefox daily use.
Firefox is growing on iPhone, but only as a WebKit shell
According to Mozilla, Firefox usage on iPhone is growing quickly around the world, and fastest of all in the European Union. Since 2024, when the EU Digital Markets Act began requiring Apple to let iPhone users choose their default browser, millions of people have picked Firefox — and Mozilla says daily use of Firefox on iOS has doubled.
The catch is that the Firefox those users run is not the full browser. Mozilla explains that Apple requires every browser on iOS to be built on WebKit, Apple's own engine. Firefox is built on Gecko, and many of its features live inside that engine, which is why the complete version of Firefox cannot easily be brought to iPhone. Mozilla points out that iPhones and iPads are the only major devices with this restriction: on every other major operating system, including Apple's own macOS, the Gecko-powered Firefox is available.
Regulators opened a door, with conditions attached
The DMA did force a partial change. Because of it, Apple began allowing alternative browser engines on iOS in the EU, and published a set of conditions companies must satisfy to ship one. When those rules appeared, Mozilla said they made the process "as painful as possible" for alternatives like Gecko. Japan has since introduced its own requirements for alternative iOS browser engines, and Mozilla says Apple applied very similar conditions there.
The result, according to Mozilla: nearly three years after Apple introduced the EU conditions and almost a year after Japan's, not a single developer has launched a non-WebKit browser on iOS. Mozilla's verdict is that Apple's conditions remain unworkable, and that compliance on paper has not delivered the change the rules were meant to produce in practice.
What makes the conditions unworkable
Mozilla says it has spent the time since the DMA took effect working behind the scenes to test and improve Apple's conditions so it could bring Gecko to iOS, and that these efforts have so far largely failed. One condition prevents the company from disclosing non-public details of the project, but Mozilla shared one concrete example of the friction involved.
To ship Gecko, Mozilla could not simply update the Firefox app people already use. It would have to build an entirely separate second Firefox app, then ask every existing user to download it, move their bookmarks, passwords and browsing history across, and manually switch over step by step.
Mozilla argues this asks far too much of people who have already made their choice, and that a significant proportion would understandably give up — including many who picked Firefox from the EU's choice screen in the first place. The company adds that this is a level of friction Apple would never accept for its own apps, and that the open door "feels more like a trap door."
Why it matters
This is a concrete test of whether platform regulation changes outcomes in practice rather than just on paper. The DMA succeeded in one respect: EU users can now choose their default browser, and enough of them chose Firefox to double its daily iOS use. But engine diversity, the deeper issue, remains untouched, because the conditions for shipping an alternative engine are, in Mozilla's telling, structured so that no independent developer can realistically meet them.
That matters for the web platform as a whole. Gecko is, according to Mozilla, the last major browser engine not developed by a big tech company, and on iOS it remains locked out in practice even where regulators have formally allowed it. Mozilla says it will keep pushing for a genuinely level playing field rather than an opening that drops independent browsers through the floor. How regulators respond to that record — two jurisdictions, several years, zero shipped alternative engines — is the question Mozilla's post leaves open.
- #firefox
- #apple
- #ios
- #browser-engines
- #digital-markets-act