TL;DR
No developer has launched a non-WebKit browser on iOS under Apple’s alternative-engine rules, according to Mozilla. Mozilla says the requirements include building a separate app for Gecko-powered Firefox, forcing users to migrate their data and switch manually; Apple’s response and the prospects for a launch are not included in the source material.
No non-WebKit browser has launched on iOS under Apple’s rules permitting alternative browser engines in the European Union and Japan, Mozilla says. The company argues that Apple’s requirements make it impractical to bring Gecko-powered Firefox to iPhone users, limiting the browser features available to them and leaving WebKit as the engine used by iOS browsers currently available.
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
Mozilla says Apple began allowing alternative browser engines in the EU following the Digital Markets Act and later introduced similar conditions in Japan after that country adopted new rules. The company says that despite those policy changes, no developer has launched a browser on iOS using an engine other than Apple’s WebKit.
The central obstacle Mozilla describes is the app structure required to use Gecko. It says it cannot simply update the Firefox app that iPhone users already have. Instead, it would have to create a separate Firefox app, then ask users to download it and move bookmarks, passwords and browsing history before switching over manually.
Mozilla says those steps could cause users to abandon the process, including people who selected Firefox through an EU browser choice screen. It also says Apple’s conditions include restrictions on disclosing non-public project information, limiting the details it can share about its work to meet the requirements. The report does not provide Apple’s account of the rules or a response from the company.
How Engine Rules Affect iPhone Users
The dispute concerns more than the name shown on a browser icon. Mozilla says many Firefox features are built into Gecko, its own browser engine, and that requiring WebKit prevents it from bringing the full range of those features to iOS. If that description is accurate, users may have a choice among browser apps without access to the same range of underlying browser technology available on other major platforms.
It also puts the practical effect of competition rules under scrutiny. A policy can permit alternative engines on paper, but its effect depends on whether developers can meet the conditions and users can adopt the resulting apps. Mozilla’s account points to installation and data-migration friction as a barrier that could reduce the value of choosing a browser through a choice screen.
Mozilla says Firefox use on iOS has grown, particularly in the EU since 2024, and that daily use has doubled. It does not give a measurement period, figures or a comparison baseline for those statements in the supplied report, so they cannot establish how much the rules changed usage.
Products Worth Considering

DJI Mini 4K Drone with 4K UHD Camera

Samsung Galaxy Tab A11+ Tablet (6GB RAM, 128GB Storage, Gray)

LG UltraGear 34-Inch Curved QHD Gaming Monitor, 160Hz, FreeSync Premium
As an affiliate, we earn on qualifying purchases.
EU and Japan Set the Policy Backdrop
Apple’s restrictions have applied to browsers on iOS, while Mozilla says Gecko-powered Firefox is available on other major operating systems, including Apple’s macOS. The company describes iPhones and iPads as unusual among major platforms because browsers there have been required to use Apple’s engine.
The EU’s Digital Markets Act led Apple to permit alternative engines in the region, subject to conditions it set. Mozilla says it criticized those conditions at the time as making the process “as painful as possible.” Japan subsequently adopted rules requiring alternative engines on iOS, and Mozilla says Apple applied very similar conditions there. The source does not specify the exact dates of the Japanese rules or provide a legal assessment of whether Apple’s terms comply with either regime.
Mozilla says it has worked behind the scenes since the DMA took effect to test and improve the conditions so it can bring Gecko to iOS, but that effort has largely failed. The source describes the company’s experience; it does not independently document each negotiation or technical test.
““as painful as possible””
— Mozilla
What the Report Leaves Unresolved
The supplied material does not include Apple’s response, the full text of its conditions, or an independent review of whether the requirements are technically necessary or proportionate. It also does not identify other developers that have tried to launch alternative engines or explain whether any are currently preparing an iOS release.
Mozilla says it would need a second app and a manual migration, but the report does not give technical details about the restriction, quantify how many users might decline to switch, or explain whether Apple could approve a different migration path. It is also unclear whether regulators in the EU or Japan have investigated Mozilla’s concerns or taken action over the conditions.
The source’s statement that nearly three years have passed since the EU conditions were introduced and almost a year since Japan’s does not come with a publication date here. Those relative timelines cannot be converted into exact dates from the supplied information.
Mozilla’s Next Push for Changes
Mozilla says it will continue pressing for changes that make alternative engines workable. The report does not announce a launch date for a Gecko-based iOS browser, say that Apple has agreed to revise its terms, or identify a scheduled regulatory decision.
The next clear developments to watch are whether Apple changes its requirements, whether regulators assess the reported barriers, and whether Mozilla or another developer announces an iOS browser built on a non-WebKit engine. Until one does, the rules’ practical effect remains limited: no such browser has launched, according to Mozilla.
Key Questions
Are there any non-WebKit browsers on iOS?
Mozilla says no developer has launched a non-WebKit browser on iOS under Apple’s alternative-engine rules. The report describes existing iOS browsers as remaining subject to Apple’s engine requirements.
Why can’t Mozilla add Gecko to its existing iPhone Firefox app?
Mozilla says Apple’s conditions mean it cannot simply update the current app to use Gecko. It says it would need to release a separate Firefox app, though the supplied report does not include Apple’s explanation of that requirement.
What would iPhone users have to do to switch, according to Mozilla?
Mozilla says users would need to download the separate app and move bookmarks, passwords and browsing history before switching manually. It argues that the added steps could discourage some users.
Do the EU and Japan allow alternative browser engines on iOS?
Apple began permitting alternative engines in the EU after the Digital Markets Act and introduced similar conditions in Japan following new rules there, according to Mozilla. The company says the conditions have not yet produced a launch.
Has Apple responded to Mozilla’s criticism?
No Apple response is included in the supplied material. It also does not say whether regulators have formally reviewed Mozilla’s concerns.
Source: blog.mozilla.org
