TL;DR
Apple’s rules allow alternative browser engines on iOS in the EU and Japan, but Mozilla says no developer has launched a non-WebKit browser under those conditions. Mozilla says a Gecko-based Firefox would require a separate app and a difficult user migration; Apple has not provided a response in the supplied material.
No developer has launched a non-WebKit browser on iOS under Apple’s alternative-engine rules in the European Union or Japan, Mozilla says, despite those rules being introduced in response to new competition requirements. Mozilla argues that Apple’s conditions make it impractical to bring its Gecko engine to iPhones, limiting what users can choose beyond browsers built on Apple’s WebKit.
Get the latest gadgets delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
Apple began allowing alternative browser engines on iOS in the EU after the Digital Markets Act required changes to its platform rules. Japan later adopted rules requiring Apple to permit alternative engines as well. Mozilla says Apple applied similar conditions in both markets. According to the company, no browser developer has managed to release a non-WebKit browser under those terms.
Mozilla says the restrictions affect more than the engine a browser uses. It says it cannot simply update the Firefox app already available on iPhone to use Gecko. Instead, it would need to create a separate Firefox app, then ask users to install it and transfer bookmarks, passwords and browsing history. The company says that process could lead people to abandon the switch, including users who selected Firefox through the EU’s browser-choice screen.
Mozilla also says its work with Apple to test and improve the conditions has so far largely failed. It did not disclose project details, citing a condition against sharing non-public information. The account and criticism are Mozilla’s description of its experience; the supplied material includes no response from Apple or an independent assessment of the rules’ effect.
What the Rules Mean for iPhone Users
The practical question is whether users can choose browsers that rely on different underlying technology, not merely different app names or interfaces. If every available iOS browser must use WebKit, Mozilla says it cannot offer the full range of Firefox features built around Gecko. That leaves iPhone users without the same engine choice available on other major operating systems, including Apple’s macOS, where Gecko-powered Firefox is available.
The issue also bears on whether competition rules produce usable alternatives. A policy may permit a new option formally while technical requirements, app separation or user-transfer steps make it difficult to adopt. Mozilla argues those barriers weaken the impact of browser-choice measures. Its account highlights a potential gap between permission on paper and a browser users can actually install and use; the supplied material does not independently establish how many users would decline to migrate.
Products Worth Considering

Logitech MX Mechanical Wireless Illuminated Keyboard, Tactile Quiet, Graphite

Apple AirPods Pro 3 Wireless Earbuds

Samsung Odyssey OLED G8 34-Inch Curved Ultra WQHD Gaming Monitor
As an affiliate, we earn on qualifying purchases.
How EU and Japan Rules Developed
Apple’s iOS browser-engine restriction has meant that competing browsers on iPhones use Apple’s engine rather than their developers’ own. Mozilla says this limits its ability to bring the same Gecko-based features available in Firefox on other platforms to iOS. The company describes iPhones and iPads as unusual among major operating systems in maintaining this restriction.
The EU’s Digital Markets Act prompted Apple to allow alternative engines under a set of conditions. Mozilla previously characterized those requirements as making the process “as painful as possible,” according to its account. Japan subsequently introduced similar requirements, and Apple set comparable conditions there. Mozilla says it has been working behind the scenes since the EU rules took effect to see whether it could meet them, but has not yet been able to launch Gecko on iOS.
Mozilla also reports that Firefox use on iOS has grown, particularly in the EU since 2024: it says daily use has doubled and millions of people have chosen Firefox. The source gives no precise measurement period or underlying figures for those claims, so they are Mozilla-reported metrics, not independently verified comparisons.
““as painful as possible””
— Mozilla
What Apple’s Conditions Still Require
The source does not provide Apple’s response, the full text of its conditions, or an independent review of Mozilla’s account. Mozilla says it cannot disclose some non-public project information, so the specific exchanges between the companies and the full set of implementation obstacles remain unclear.
It is also not clear whether another developer is preparing a non-WebKit browser, whether any application has been submitted for approval, or whether Apple has changed its requirements since they were introduced. Mozilla’s statement that no developer has launched such a browser describes the reported status; it does not establish what may be under development. The source does not give a publication date, limiting how precisely that status can be dated.
Mozilla’s Push for Easier Access
Mozilla says it will continue pressing for conditions it considers a real level playing field and for the ability to bring Gecko to iOS. The supplied material does not identify a formal deadline, a pending regulatory decision, or a scheduled Apple policy change. The next clear milestone would be a developer launching an alternative-engine browser or a regulator or Apple changing how the rules are applied.
For now, users should not assume that EU or Japanese rules have already produced a Gecko-based Firefox for iPhone. Mozilla’s account says the option has not reached users, and the source provides no confirmed launch date. Whether Apple will revise the conditions, or another developer will meet them, remains open.
Key Questions
Are there non-WebKit browsers on iOS?
Mozilla says no developer has launched one under Apple’s alternative-engine rules in the EU or Japan. The supplied material does not identify any exception.
Why can’t Firefox on iPhone simply switch to Gecko?
Mozilla says Apple’s conditions would require a separate app, rather than an update to the existing Firefox app. Users would then need to install it and move their bookmarks, passwords and history.
Do the EU and Japan rules permit other browser engines?
Apple began allowing alternative browser engines in the EU after the Digital Markets Act and introduced similar conditions in Japan following that country’s rules, according to Mozilla. The company says the requirements have not yet resulted in a non-WebKit launch.
Has Apple responded to Mozilla’s criticism?
The supplied source material contains no response from Apple. It also does not include the complete conditions or independent findings about their effects.
Source: blog.mozilla.org
