← Back to BLACKWIRE VOLT BUREAU REGULATORY IMPACT iPhone screen showing multiple browser icons with Apple’s WebKit logo overlay

Apple’s WebKit requirement forces all iOS browsers, including Firefox, to use the same rendering engine.

APPLE'S iOS RULES BLOCK NON-WEBKIT BROWSERS DESPITE EU DMA

*Firefox usage on iPhone has doubled since the EU Digital Markets Act forced Apple to expose a default‑browser choice in 2024. Yet Apple’s engine restrictions keep Gecko off iOS, turning a regulatory win into a technical dead‑end.*

By VOLT Bureau - BLACKWIRE  |  November 20, 2026, 18:00 CET  |  Apple, iOS, WebKit, Firefox, EU DMA

Apple’s iOS ecosystem has long forced every browser to run on WebKit, sidelining any alternative rendering engine. The EU Digital Markets Act, enforced in 2024, forced Apple to expose a default‑browser selector, and millions of European users quickly chose Firefox. Daily Firefox usage on iPhone has doubled, signaling strong demand for an independent browser experience. Yet Apple’s response was to publish a set of conditions that make any non‑WebKit engine, such as Mozilla’s Gecko, practically impossible to deploy. Nearly three years after the EU’s mandate and almost a year after Japan introduced similar rules, not a single developer has managed to launch a non‑WebKit browser on iOS.

Why hasn't Apple allowed a Gecko browser on iOS?

Apple requires every iOS browser to use its WebKit engine. The EU DMA and Japan's new rules technically permit alternative engines, but Apple attached conditions that make implementation impossible. Mozilla must create a brand‑new app to run Gecko, cannot simply update the existing Firefox, and must force users to migrate bookmarks, passwords and history manually. The friction level Apple would never accept for its own apps becomes a barrier for independent browsers. As a result, no developer has succeeded in launching a non‑WebKit browser on iOS in nearly three years in the EU and almost a year in Japan.

What does the EU DMA actually require?

The Digital Markets Act, effective in 2024, obliges Apple to let users pick a default browser on iOS. Millions of EU users have chosen Firefox, and daily Firefox usage on iPhone has doubled since the rule took effect. The law does not dictate which engine the browser must use, only that a choice be available. Apple’s response was to publish a set of conditions for alternative engines, but those conditions have proven unworkable, leaving the regulatory intent unfulfilled.

Apple’s conditions turn a regulatory opening into a trap door, leaving independent browsers stranded on iOS.

Technical hurdles imposed by Apple

Apple’s conditions forbid developers from disclosing non‑public project details and demand a separate app for any non‑WebKit engine. Mozilla would need to build a second Firefox, ask every user to download it, and manually transfer data. This creates a “trap door” where the opening exists on paper but collapses in practice. The required user friction exceeds what Apple tolerates for its own apps, effectively blocking independent browsers from gaining traction.

How is Mozilla responding?

Since the DMA’s rollout, Mozilla has been testing Apple’s conditions behind the scenes. Their efforts have largely failed, prompting a public call for a genuine level playing field. Mozilla argues that Firefox users on iPhone deserve the full Gecko engine, the last major browser engine not owned by a big‑tech company. The organization vows to keep pushing for workable rules, warning that the current “open door” drops independent browsers through the floor.

Frequently asked questions

When did the EU Digital Markets Act require Apple to let users choose a default browser?

The EU DMA started requiring Apple to let people choose their default browser in 2024.

What condition does Apple impose on using Gecko on iOS?

Apple requires developers to build a separate app for Gecko, forcing users to download it, move bookmarks, passwords and history, and manually switch over.

Has any developer launched a non-WebKit browser on iOS since the new rules?

No, not a single developer has been able to launch a non-WebKit browser on iOS in the three years since the EU conditions and almost a year in Japan.

The gap between policy and practice on iOS remains stark. While the DMA succeeded in giving users a choice on paper, Apple’s engine lock‑down keeps that choice hollow. Unless Apple revises its conditions or regulators enforce stricter compliance, Firefox and other independent browsers will continue to be denied the full feature set users expect. Mozilla’s push for a real level playing field underscores a broader battle over digital sovereignty in the mobile browser market.

Sources: [Mozilla Blog – Why there are still no non-WebKit browsers on iOS]