Brussels Breaks the WebKit Wall: EU Orders Apple to Open iOS to Rival Browsers

The DMA's First True Teeth

In a decision poised to send shockwaves through Silicon Valley, the European Commission today, August 5, 2026, delivered its most significant enforcement action under the Digital Markets Act (DMA). Brussels has ordered Apple to cease its long-standing practice of forcing all web browsers on iOS and iPadOS to use its native WebKit rendering engine. The ruling, announced by Executive Vice-President Margrethe Vestager, compels Apple to allow competing browser engines, such as Google's Blink and Mozilla's Gecko, to run natively on iPhones and iPads within the EU. The decision is backed by a staggering €2.7 billion fine, signaling the Commission's newfound willingness to levy severe penalties against designated "gatekeepers" who fail to comply with the landmark legislation.

The End of the Walled Garden's Tallest Tower

For over a decade, the App Store review guidelines have contained a clause that, while seemingly innocuous, has been a major source of frustration for developers and a cornerstone of Apple's platform control. Guideline 2.5.6 mandates that all apps browsing the web must use the WebKit framework and WebKit JavaScript. This meant that while you could download Google Chrome or Mozilla Firefox from the App Store, you weren't actually using their core technology. You were using a reskinned version of Safari.

This "browser engine mandate" ensured Apple dictated the pace of web innovation on its mobile platform. If a new web standard, API, or performance feature wasn't implemented in WebKit, it was inaccessible to every single iOS user, regardless of their chosen browser app. Critics argued this stifled competition and kneecapped the potential of Progressive Web Apps (PWAs)—websites that can be 'installed' on a home screen and function like native apps—forcing developers to build expensive native apps and pay Apple's 15-30% App Store commission.

This wasn't just about browsers; it was about Apple unilaterally defining what the 'web' could and could not do on the world's most profitable mobile platform.

What the Ruling Demands

The Commission's ruling is surgically precise. It finds Apple in breach of Article 5(7) of the DMA, which requires gatekeepers to allow and technically enable the installation and use of third-party software applications or software application stores. The EC's investigation concluded that by restricting browser engines, Apple was effectively preventing browsers from differentiating themselves in core functionality, thereby limiting consumer choice and innovation.

The order contains two primary components:

• The Mandate: Apple must, within 90 days, update iOS and its developer tools to allow third-party browser engines to be submitted to the App Store. This includes providing them with the same level of API access and system integration that Safari currently enjoys.
• The Fine: A €2.7 billion penalty, calculated as a percentage of Apple's global turnover. This is one of the largest antitrust fines ever levied by the EU and serves as a clear warning to other designated gatekeepers like Google, Amazon, and Meta.

In her press conference, Vestager was resolute. "For too long, a single gatekeeper has held the keys to the mobile web for millions of European citizens," she stated. "Today's decision restores competition and opens the door for a new era of innovation. The DMA is not a paper tiger; it is the rule of law in our digital single market."

"A Win for a Truly Open Web": The Technical Implications

For web developers, this decision is a watershed moment. The limitations of WebKit on iOS have been a notorious bottleneck. Features like full access to background sync, push notifications for PWAs, and certain graphics APIs that are standard in Chrome's Blink engine have been either missing or delayed on iOS. This forced developers to maintain separate, often inferior, web experiences for Safari users or abandon the web in favor of native apps.

"This completely changes the calculus for web development," explained Sarah Reed, a principal analyst at Forrester Research. "The ability to use Blink or Gecko means developers can write one high-performance PWA that works identically across Android and iOS. It challenges the primacy of the App Store as the only way to deliver rich application experiences on the iPhone. We expect to see a surge in investment in the PWA ecosystem."

This means users could soon install a version of Chrome on their iPhone that is genuinely Chrome, complete with its V8 JavaScript engine, extension support (though the extent of this will depend on Apple's implementation), and feature release schedule. The performance and capability gap between native apps and web apps on iOS is set to narrow dramatically.

Apple's Defense and the Security Argument

Apple has consistently defended its WebKit mandate on the grounds of user security and privacy. The company argues that by controlling the single engine that interprets web code, it can ensure a consistent, secure, and privacy-preserving experience for all users. By tightly integrating WebKit with the OS, Apple can implement system-level protections like Intelligent Tracking Prevention (ITP) and sandboxing that apply to all web browsing activity.

In a pre-emptive statement released on its newsroom, Apple reiterated this stance. "We are deeply concerned by this decision, which prioritizes the business models of a few large companies over the security and privacy of our users," the statement reads. "The WebKit engine is engineered to be the most secure and power-efficient mobile browser engine in the world. Forcing us to abandon this integrated approach will create new avenues for malware and tracking, degrading the iOS experience. We will be appealing this decision."

While the security argument has merit—unfettered access could indeed open new attack vectors if not managed properly—critics argue it has also been a convenient shield for anti-competitive behavior. The DMA requires Apple to provide access, but it doesn't prevent them from implementing robust security reviews and permissions for apps that use third-party engines.

Who Wins, Who Loses?

The most immediate and obvious winner is Google. Its Blink engine holds an overwhelming market share on every platform except iOS. This ruling allows Google to extend its de facto monopoly on the web's infrastructure to Apple's lucrative user base, a prospect that worries some web purists who fear over-reliance on a single company's technology. Mozilla's Firefox, running its Gecko engine, also gets a fighting chance to gain a real foothold on mobile.

Web developers are clear winners, gaining freedom and new capabilities. Users stand to benefit from more choice and potentially better, faster web apps. The biggest loser is Apple. The company loses a critical control point over its ecosystem. If users can get app-like experiences from the web, they are less reliant on the App Store, which in turn threatens Apple's highly profitable services revenue. This is not just a technical change; it's a fundamental challenge to the App Store business model.

This ruling is a test of the DMA's power to reshape digital markets. While Apple will undoubtedly fight this decision in the European courts for years to come, it must comply with the order in the interim. The walls of the garden are, for the first time, being meaningfully lowered. What happens next—whether a flourishing new ecosystem of browsers emerges or one giant simply replaces another—will determine the future of the mobile web for years to come.