Alternative Browser Engines on iOS Still Don’t Exist

Firefox and alternative browser engines on iOS blocked by Apple's conditions

Nearly three years after Apple opened the door to alternative browser engines on iOS in the European Union, nobody has shipped one. Mozilla, the company behind Firefox, says the conditions Apple attached to that opening are unworkable, and it wants regulators to judge the rules by results rather than paperwork.

What Apple changed, and where

For years Apple required every iPhone browser to run on WebKit, its own engine. Chrome, Firefox, Edge and the rest were skins over the same core. The EU’s Digital Markets Act (DMA) changed that. Apple began allowing other engines on iOS in the EU and published a list of conditions for companies that wanted to bring their own.

Japan later passed rules of its own that require alternative engines on iOS. Apple applied very similar conditions there. The EU rules are almost three years old and the Japanese ones almost a year old. In that time, according to Mozilla, not a single developer has launched a non-WebKit browser on the iPhone.

Why Firefox cares

Firefox on iPhone is growing quickly worldwide, and especially in the EU. Since 2024 the DMA has required Apple to let people pick a default browser. Millions have chosen Firefox, and Mozilla says daily use on iOS has doubled.

That demand runs into a ceiling. Many Firefox features live inside Gecko, the engine Mozilla builds, so the iPhone version can’t offer everything that exists elsewhere. Mozilla points out that iPhones and iPads are the odd ones out. On every other major platform, including Apple’s own macOS, people can run the Gecko-powered Firefox.

Gecko is also the last major browser engine not developed by a big tech company. If it never reaches iOS, the engine choice on iPhone stays effectively a one-horse race.

The second-app problem

Mozilla has spent the time since the DMA took effect testing Apple’s conditions and trying to get them improved. It says those efforts have largely failed. One condition bars it from disclosing non-public details of the project, so it can share only an example.

The example is a big one. To use Gecko on iOS, Mozilla couldn’t simply update the Firefox app that people already have. It would have to build a separate app, effectively a second Firefox. Every existing user would then need to download the new app, move over their bookmarks, passwords and history, and switch by hand.

That is a lot to ask. Mozilla expects a significant share of users to give up partway, including many who picked Firefox from the EU’s browser choice screen in the first place. It also notes that Apple would never impose that level of friction on its own apps.

Rules on paper versus rules in practice

Mozilla’s argument comes down to a test. A rule is only as good as the change it produces, and compliance on paper doesn’t count if nobody can use the option. By that measure, it says, the browser-engine rules haven’t delivered what the DMA intended.

It isn’t the first time the company has criticized the setup. When Apple introduced its conditions, Mozilla said they made it “as painful as possible” for alternatives like Gecko. Its latest account is that the open door feels more like a trap door: an opening that looks real but drops independent browsers through the floor.

Who is affected

  • iPhone users in the EU and Japan, who can pick a default browser but still can’t get a different engine underneath it.
  • Browser makers, who can’t bring their full feature sets to iOS without building and promoting a second app.
  • Regulators in both regions, who wrote the rules and now have evidence on how they play out in practice.

What happens next

Mozilla says it will keep pushing for a level playing field. The company hasn’t said it is dropping the Gecko project, and it continues to test and negotiate Apple’s conditions behind the scenes.

The next moves belong to Apple and to the EU and Japanese authorities. If Apple changes the conditions, for example by letting an existing app switch engines without a second download, a first non-WebKit browser on iOS could finally appear. If it doesn’t, the question of whether the DMA’s browser provisions work as intended is likely to be raised again with regulators.

For now, an iPhone owner who wants Firefox gets Firefox on WebKit, and that is still the only choice on offer.

Source: blog.mozilla.org

Written by

Saksham Bhargava

Saksham Bhargava runs Alteroid and has been writing about consumer technology for over five years, covering iPhone, Android, Windows, AI tools and gaming. With an MCA and six years of hands-on web development experience, he tests the features he writes about on his own devices and focuses on clear, practical guides that solve real problems. Away from the screen, he enjoys travelling to places most tourists skip.