Newshot

Why there are still no non-WebKit browsers on iOS

Original text(via Hacker News)

Why there are still no non-WebKit browsers on iOS

Firefox on iPhone is growing fast across the world. This is especially true in the EU since 2024, when the EU Digital Markets Act (DMA) started requiring Apple to let people choose their default browser; millions have picked Firefox, and daily use on iOS has doubled. People want to choose the browser on their phone.

But there remains an important limitation to what is available on iPhones: Apple forces all browsers on iOS to be built on Apple’s own browser engine.

This has meant that companies like Mozilla cannot easily bring the full range of Firefox features and functionality to iPhone users because many of these are built within our browser engine, Gecko. iPhones and iPads are unique in having this restriction. On all other major operating systems, including Apple’s macOS, people can access the Gecko-powered version of Firefox.

As a result of the DMA, Apple began allowing alternative browser engines on iOS in the EU. It published a set of conditions that companies like Mozilla must comply with to bring their own browser engine. At the time we said Apple’s rules made it “as painful as possible” for alternatives like Gecko. In the meantime, Japan also introduced new rules requiring alternative browser engines on iOS. Apple applied very similar conditions in Japan to those in the EU.

Nearly three years since Apple introduced these conditions in the EU and almost a year since Japan, not one developer has been able to launch a non-WebKit browser on iOS. The reason is simple: Apple’s conditions remain unworkable. The real test of any rule is whether it delivers the change it was meant to achieve in practice. Compliance on paper alone falls short of that test.

Since the DMA came into effect we’ve been working behind the scenes to test and improve Apple’s conditions so that we can bring Gecko to iOS users. Those efforts have so far largely failed.

One of the conditions requires us not to disclose non-public information related to the project, but here’s an example of what we are up against: to use Gecko, we can’t simply update the Firefox app people already use and love. We’d have to build a whole separate app, a second Firefox. Then we’d have to ask every Firefox user to download it, move their bookmarks, passwords and history across, and manually switch over, step by confusing step.

That’s a lot to ask of people who already made their choice. A significant proportion of people would understandably give up, including many who picked Firefox from the EU’s choice screen.

The conditions Apple imposes, including a level of user friction Apple would never accept for its own apps, mean that the open door feels more like a trap door.

Firefox users on iPhone chose an independent browser. They should get everything that comes with it, including Gecko, the last major browser engine not developed by a big tech company. We’ll keep pushing for a real level playing field, not an opening that drops independent browsers through the floor.

The text above was extracted automatically from the source page and may miss images, tables or code blocks. The original is authoritative.

Published by Hacker News
This site only summarises and aggregates; copyright stays with the original author. Headlines and summaries follow the source — where they differ, the original wins.
Read the original ↗