Mozilla says no non-WebKit iOS browser has launched under Apple's EU and Japan rules

Mozilla says no non-WebKit iOS browser has launched under Apple's EU and Japan rules

Mozilla has published a blog post asking why iPhones still have no browsers built on anything but Apple's engine. Its answer: Apple's conditions for alternative engines remain unworkable.

The post opens with Firefox's growth on iPhone. Mozilla says this is especially true in the EU since 2024, when the Digital Markets Act (DMA) started requiring Apple to let people choose their default browser. Millions have picked Firefox, it says, and daily use on iOS has doubled (no baseline or absolute figure is given). Mozilla reads this as proof that people want to choose the browser on their phone.

The limit it points to is that Apple forces all browsers on iOS to be built on Apple's own browser engine. Many Firefox features are built inside Mozilla's engine, Gecko, so the company says it cannot easily bring the full range of Firefox features to iPhone users. Mozilla stresses that iPhones and iPads are unique in this. On all other major operating systems, including Apple's macOS, people can use the Gecko-powered Firefox.

As a result of the DMA, Apple began allowing alternative browser engines on iOS in the EU and published conditions that companies must meet to bring their own engine. Mozilla says it said at the time that the rules made things 'as painful as possible' for alternatives like Gecko. Japan has since introduced new rules requiring alternative browser engines on iOS, and Mozilla says Apple applied very similar conditions there.

The outcome, in Mozilla's words: nearly three years after Apple introduced the conditions in the EU, and almost a year after Japan, not one developer has been able to launch a non-WebKit browser on iOS. Mozilla argues that the real test of a rule is whether it delivers the intended change in practice, and that compliance on paper alone falls short. Since the DMA came into effect, it says, it has worked behind the scenes to test and improve Apple's conditions so that Gecko can reach iOS users. Those efforts have so far largely failed.

Mozilla gives one example of the obstacle. One of the conditions requires it not to disclose non-public information about the project, but it says that to use Gecko it could not simply update the Firefox app people already use. It would have to build a whole separate app, a second Firefox. It would then have to ask every Firefox user to download it, move their bookmarks, passwords and history across, and switch over manually, step by step. Mozilla expects a significant proportion of people would understandably give up, including many who picked Firefox from the EU's choice screen.

It concludes that the conditions, including a level of user friction Apple would never accept for its own apps, make the open door feel more like a trap door. Firefox users on iPhone chose an independent browser, Mozilla says, and should get everything that comes with it, including Gecko, which it calls the last major browser engine not developed by a big tech company. It says it will keep pushing for a real level playing field.

Key facts

  • Mozilla says that nearly three years after Apple introduced its alternative-engine conditions in the EU, and almost a year after Japan, not one developer has launched a non-WebKit browser on iOS.
  • Mozilla's example: to use Gecko it would have to build a separate second Firefox app and ask every user to download it and manually move bookmarks, passwords and history.
  • Apple applied very similar conditions in Japan to those in the EU, according to Mozilla.
  • Mozilla says its behind-the-scenes efforts to test and improve the conditions have so far largely failed.
  • Mozilla says Firefox daily use on iOS has doubled and millions of EU users have picked Firefox, though it gives no baseline or exact figures.

Why it matters

The EU's DMA and Japan's rules were meant to open iOS to browsers that do not use Apple's engine. By Mozilla's account, the rules exist on paper but have produced no working non-WebKit browser in nearly three years in the EU and almost a year in Japan. Mozilla calls Gecko the last major browser engine not developed by a big tech company, and says iPhones and iPads are the only major platforms where Firefox cannot run on it.

Who it affects

Firefox users on iPhone and iPad, who in Mozilla's words chose an independent browser but cannot get Gecko. Mozilla itself, and any other developer wanting to ship their own engine on iOS in the EU or Japan. Regulators and lawmakers judging whether the DMA and Japan's rules change anything in practice.

How to use it

There is nothing to install or adopt here. The post is an advocacy statement, not a product release. It gives no timeline for when Mozilla might bring Gecko to iOS. Developers weighing an alternative engine on iOS can note Mozilla's reported obstacles: a separate app, manual user migration, and a non-disclosure condition on non-public project information.

How solid is it

This is a first-party post from Mozilla, written in the voice of the company, and it is a party with a direct interest in the outcome. The headline claim is a flat statement that not one developer has launched a non-WebKit browser on iOS. The post does not list Apple's conditions in full, only the separate-app requirement and the non-disclosure clause. The doubling of Firefox's daily use on iOS comes with no baseline. No Apple response is included.

Risks and caveats

Mozilla describes Apple's conditions only in part. One of them requires it not to disclose non-public project information. The post does not name other browser vendors that tried and failed, and mentions no legal action or filing with the European Commission. Whether the conditions are unworkable for others, or only for Gecko as Mozilla describes it, is not addressed.

“The conditions Apple imposes, including a level of user friction Apple would never accept for its own apps, mean that the open door feels more like a trap door.”

— Mozilla, blog post