← All stories
● Covered by 1 source · 1 reportMedium impact1 negative

Mozilla States Apple's iOS Browser Engine Rules Remain Unworkable for Non-WebKit Browsers

🔄 Updated 8h ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Apple forces all iOS browsers to use its WebKit engine.
  • EU and Japan regulations require Apple to allow alternative browser engines.
  • Apple's conditions for alternative engines are deemed unworkable by Mozilla.
  • No non-WebKit browser has launched on iOS since the rules were introduced.

Persistent WebKit Restriction on iOS

Despite growing user preference for browsers like Firefox on iOS, particularly in the EU following the Digital Markets Act (DMA), Apple continues to mandate the use of its WebKit browser engine for all browsers on its mobile operating system. This restriction prevents companies like Mozilla from integrating their full browser engine capabilities, such as Gecko, into their iOS applications, unlike on other operating systems including macOS.

Regulatory Efforts and Apple's Conditions

The EU's DMA and similar new rules in Japan require Apple to permit alternative browser engines on iOS. In response, Apple published a set of conditions for developers wishing to use their own engines. Mozilla previously characterized these rules as making it 'as painful as possible' for alternatives. Similar conditions were applied in Japan.

Unworkable Implementation Challenges

Nearly three years after the EU conditions and almost a year after Japan's, no developer has managed to launch a non-WebKit browser on iOS. Mozilla attributes this failure to Apple's conditions remaining unworkable in practice. Mozilla's efforts to test and improve these conditions have largely failed.

Example of a Key Obstacle

One significant condition requires developers to build an entirely separate application for an alternative browser engine, rather than updating an existing app. For Firefox, this would mean users would need to download a second Firefox app, manually migrate their data (bookmarks, passwords, history), and switch over, creating a confusing and burdensome process that would likely deter many users.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 21

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

Mozilla reports that despite new regulations in the EU and Japan, no developer has successfully launched a non-WebKit browser on iOS due to Apple's restrictive conditions. These conditions, which include requiring a separate app for alternative engines, prevent Mozilla from bringing its Gecko engine to iOS users.