Mozilla Explains Why iPhone Still Has No Browsers Using a Non-Apple Engine
Mozilla explains why browsers using engines other than WebKit still haven’t launched on iPhone. Firefox on iOS uses WebKit, so testing in it doesn’t replace testing in Firefox with Gecko.
On November 20, 2026, Mozilla explained why browsers using engines other than WebKit still haven’t launched on iPhone. Apple has allowed alternative engines in the EU and Japan, but Mozilla believes the conditions attached to their use make it difficult to get such a browser into users’ hands. The practical takeaway for website testing: Firefox on iPhone is no substitute for testing in Firefox with Gecko.
You Can Choose Firefox, but Not Its Engine
Since 2024, the Digital Markets Act (DMA) has required Apple to let users in the EU choose their default browser. Mozilla says millions of people have chosen Firefox and daily usage of the browser on iOS has doubled. But choosing the app doesn’t change its engine: Firefox for iPhone runs on WebKit, while many Firefox features are built on Mozilla’s own engine, Gecko.
This limitation applies to iPhone and iPad. On other major operating systems, including macOS, Firefox is available with Gecko. So someone who chooses Firefox on their phone doesn’t necessarily get the same set of features as someone using it on another device. Mozilla says it can’t simply bring all the functionality built into Gecko over to iPhone.
After the DMA took effect, Apple allowed alternative engines on iOS in the EU, but set conditions for developers. Requirements to allow such engines later emerged in Japan; according to Mozilla, Apple introduced very similar conditions there. Mozilla says no browser using an alternative engine has launched in either the EU or Japan—nearly three years after the conditions were introduced in the EU and nearly a year after they appeared in Japan.
There’s no contradiction between formal permission and the absence of releases. Mozilla’s dispute with Apple is about whether developers can make use of that permission in practice. The company argues that the rules should be judged not only by what they say, but by whether they have enabled developers to release a browser with a different engine.
Why Mozilla Can’t Just Update Firefox
Mozilla says it has tried to examine Apple’s conditions and secure the changes needed to release Gecko on iOS since the DMA took effect. So far, those efforts have largely been unsuccessful. The company hasn’t disclosed every detail: one of the conditions restricts the disclosure of nonpublic information related to the project.
One example Mozilla does give concerns existing Firefox users. It can’t update the installed app to switch it to Gecko. Instead, it would have to release a second app. Users would then need to download it, transfer their bookmarks, passwords, and history, and manually switch to the new version.
Mozilla expects a substantial share of users not to make the switch. That could include people who have already chosen Firefox through the browser choice screen in the EU. For them, the engine wouldn’t change with a routine update: they would have to find and install another app, then transfer their data.
Mozilla isn’t claiming that Apple prohibits alternative engines altogether. Its objection is narrower: the proposed route creates obstacles both to releasing the app and to getting users to switch. The company points to the absence of browsers using other engines as evidence that formal permission has yet to produce results.
What This Means for Website Testing
If a team tests a website in Firefox on iPhone, it’s testing in a WebKit-based browser, not in Gecko. When planning tests, that distinction matters more than the app’s name: testing in one version of Firefox doesn’t replace testing in the other when you need to understand how a site behaves across engines.
For a site owner, this means a report saying “tested in Firefox” may not be specific enough. It’s worth clarifying which device was used and which engine was running before making a decision about supporting a page or feature. For developers, that distinction helps avoid presenting an iPhone test result as a Gecko test result.
Mozilla’s post does not, however, list specific web features that behave differently or describe bugs on websites. It doesn’t establish that any particular feature will break in Firefox for iPhone. It sets a narrower boundary: test results from WebKit cannot automatically be applied to Gecko, or vice versa.
My Take: Formal Permission Isn’t Enough
I would separate Mozilla’s interest in promoting its own engine from its argument about users switching. The first is obvious, but the second is concrete enough: if changing engines requires a separate app and a manual data transfer, permission in the rules alone isn’t enough to consider the problem solved.
For now, I wouldn’t plan on an alternative launching soon. It makes more sense to judge progress by browsers that have actually been released and by how easy it is for their users to switch. According to Mozilla, there is still no browser with a different engine on iOS in the EU or Japan.
Sources
Where the news comes from. The text is a retelling in the author’s own words; the facts come from the source, the opinion is the author’s.
- Why there are still no non-WebKit browsers on iOS blog.mozilla.org
Senior full-stack developer
I design and maintain web applications; in recent years I've spent more time untangling legacy code than starting from scratch. Before choosing a technology, I ask who will maintain it.
All posts by the authorRelated articles
Mozilla Introduces Firefox Enterprise with Browser Management on Company Infrastructure
Mozilla has introduced Firefox Enterprise, a centralized browser management solution that can be deployed on company infrastructure. It includes policy controls, data protection, and access controls for internal apps.
Bez Generates a Browser Engine from Web Specifications and Tests
Bez builds a browser engine from web specifications, checking its results against Chromium, Firefox, and WebKit. The project is still at an early stage, and its published figures do not mean the engine is ready.
Firefox Strengthens Protection Against Browser Fingerprinting
Mozilla has limited the information that helps websites recognize Firefox users without cookies. The new measures could affect analytics and visitor identification systems.
Discussion 5
Boris Unanyan
ну, one extra testing gotcha: browser sniffing can’t tell you whether Firefox is actually running Gecko on iOS, so don’t treat a “Firefox” user-agent as proof that Gecko-specific behavior was exercised. same app name, different engine — because apparently browser testing needed a plot twist.
Inês Ribeiro
@boris.uty So the Firefox icon is basically wearing a Gecko costume on iPhone 😅 User-agent sniffing gets the name tag, but not the engine backstage.
Murat Osmonov
That distinction matters when we’re signing off a site: a Firefox user-agent on iPhone only confirms the app, not Gecko, so it can hide an engine-specific bug until it reaches desktop users. I’d keep the test matrix explicit—Firefox on iOS for the WebKit path, and Firefox with Gecko on another platform—and budget for both rather than assuming one test covers them.
Ketevan E. — Tbilisi
ну, would you also keep separate sign-off notes for Firefox on iOS and Gecko, rather than just two rows in the test matrix? Easy for someone to see “Firefox passed” later and miss which engine actually got exercised.
Khan Serikov
@ketevan.e I’d keep separate sign-off notes, not just separate rows: record the app, OS and engine actually exercised. “Firefox passed” is the kind of tidy summary that looks fine until a Gecko-specific bug turns up and nobody can tell what was tested.