The writing is on the wall for Apple’s iOS browser dominance, and it’s being written about by regulatory bodies around the world. For more than a decade, Apple has maintained a tight grip on iPhone web browsing by forcing all browsers (Chrome, Firefox, Edge, you name it) to use Safari’s WebKit engine under the hood. But that’s about to change, whether Apple likes it or not.
Several governments are now demanding that Apple open iOS to third-party browser engines, with enforcement deadlines looming as late as 2025. From the EU’s Digital Markets Act to the UK’s new Strategic Market Status framework, regulators are essentially telling Apple: play fair or face fines worth billions. Sound familiar? It’s the same pattern we’ve seen with app store policies, but this time the stakes seem even higher.
The European Commission appointed Apple as a guardian under the Digital Markets Act on September 6, 2023, specifically targeting iOS, Safari, and the App Store. The UK Competition and Markets Authority concluded that Apple’s WebKit restriction “harms competition” and “limits the ability of rival browser vendors to innovate.” Meanwhile, researchers from Georgia Tech and Ruhr University published findings showing how Apple’s browser engine monopoly creates unique security vulnerabilities that do not exist on other platforms.
What Apple’s browser crash really costs users
Here’s what most iPhone users don’t realize: when you download Chrome or Firefox on iOS, you don’t actually get Chrome or Firefox. You will get Safari with a different coat of paint. The group Open Web Advocacy found that this restriction is “unique to Apple and no other gatekeeper imposes such a restriction.”
This architectural restriction creates a cascade of missing features that work perfectly well on Android or desktop. Chrome’s superior password management? No. Firefox’s advanced privacy controls? It’s not happening. The UK CMA investigation specifically noted how this “prevents rival browsers from introducing unique features or optimizations to iPhones and iPads, regardless of their capabilities on other platforms.”
These limitations create deeper vulnerabilities in the ecosystem that extend beyond the missing amenities. Recent vulnerability research revealed that malicious websites could access data from Gmail or other sensitive sites through Safari’s WebKit engine on newer Apple processors. Here’s the trick: This attack “only works on Safari (and all browsers on iOS due to Apple’s browser engine ban)”, but does not work on Chrome, Firefox, or other browsers when they can use their own engines on different platforms.
The WebKit browser engine has been identified as “a significant vulnerability, with exploits such as CVE-2024-23222 allowing attackers to execute arbitrary code on devices.” This creates a security paradox: Apple’s justification for browser engine control focuses on security, but that same architectural restriction creates a vulnerability choke point. Apple recently patched a critical zero-day vulnerability that was actively exploited in the wild, targeting the same WebKit engine that powers all browsers on iOS.
The crisis of regulatory deadlines is real
Multiple app schedules are converging on Apple faster than iOS update notifications. The UK inquiry has a legal deadline of October 22, 2025 to make its decision on the status of the strategic market. The European Commission has set specific deadlines throughout 2025 and 2026 for Apple to implement interoperability measures, and some iOS notification features will need to be implemented by June 1, 2026.
These are not kind suggestions. Companies designated with strategic market status in the UK face penalties of “up to 10% of the company’s global turnover” for breaches. The EU has already opened preliminary infringement proceedings against Apple for not fully complying with DMA obligations.
Apple has already started making changes, but they are minimal. In iOS 17.4, Apple introduced “new frameworks and APIs for alternative browser engines,” but only in the EU and with significant restrictions. Mozilla’s implementation problems reveal why Apple’s minimal changes don’t satisfy regulators: The company “expressed extreme disappointment” with Apple’s implementation, calling it designed to “force a standalone browser like Firefox to build and maintain two separate browser implementations.”
The European Commission closed its investigation into Apple’s browser choice screen after Apple “changed its browser choice screen, simplifying the user experience when selecting and setting a new default browser on the iPhone.” However, researchers continue to investigate other WFD compliance issues, showing that regulatory pressure extends far beyond superficial interface changes.
What this means for your iPhone experience
The regulatory push is accelerating beyond what Apple initially estimated. Even as Apple loosens restrictions, Open Web Advocacy’s research shows that Apple’s rules still “force browser vendors to abandon all their existing EU users if they want to offer an engine other than WebKit.”
This abandonment requirement destroys innovation cycles before they begin. Browser makers face an impossible choice: maintain continuity for current users or experiment with next-generation capabilities in alternative engines. The Firefox dilemma illustrates what this means for the broader competitive landscape: Companies must essentially rebuild their entire iOS presence from scratch to access the browser’s modern capabilities, while Apple faces no such burden with Safari.
The revenue at stake reveals Apple’s strategic calculations. Safari “represents between 14% and 16% of Apple’s annual operating profit and generates $20 billion a year in search engine revenue for Google.” This transforms the debate over browser engines from technical architecture to a platform control strategy: for every 1% of browser market share Apple loses, they stand to lose “$200 million in revenue per year.” These figures explain why Apple’s compliance efforts are focused on maintaining control rather than enabling genuine competition.
Once real browser competition comes to iOS, expect really different browsing experiences. Chrome could finally offer all of its syncing features, Firefox could offer its wrapper tabs for more privacy, and new browsers could experiment with features impossible under the limitations of WebKit. Web apps (those website-based apps that you can add to your home screen) would finally work properly on iOS instead of being artificially limited by WebKit restrictions.
Where Apple’s browser strength goes from here
Rather than increasing pressure, the regulatory landscape is evolving toward coordinated enforcement across multiple jurisdictions. The United Kingdom launched investigations into Apple and Google under the Digital Consumer, Competition and Markets Act which “came into force on January 1, 2025.” Several countries are closely following these procedures, creating a model for global browser competition rules that extends beyond individual regulatory responses.
Apple’s strategy appears to be a minimal compliance scenario: make enough changes to avoid massive fines while preserving as much control as possible. The company has allowed alternative browser engines in the EU, but with strict requirements that include maintaining “90% web platform testing” and updating engines within 15 days of new releases. This approach reveals Apple’s broader platform control philosophy: compliance through complexity rather than genuine openness.
PRO TIP: If you’re in the EU and want to try alternative browser engines on iOS, check if your device is running iOS 17.4 or later; that is the minimum requirement for the new capabilities.
The strategic question is not whether Apple can maintain different rules for different regions in the long term; is whether managing separate versions of iOS with different browser capabilities becomes more expensive than global policy standardization. Managing fragmented compliance across multiple regulatory frameworks while preserving consistency of the user experience presents operational challenges that worsen as more countries adopt similar regulations. Over time, Apple may have to choose between global consistency and regulatory compliance, and compliance is winning.
The December deadlines mentioned in various investigations represent only the beginning of a longer transformation. Current deadlines extend to the end of 2025 and beyond, with the UK consultation ending “at 5pm on 20 August 2025” and implementation requirements extending to 2026. These deadlines set precedents that other regulatory bodies around the world are likely to adopt, creating momentum for global browser engine policy standardization.
For iPhone users, this regulatory pressure campaign represents the best opportunity in years for genuinely competitive mobile browsing. Whether Apple accepts this change or continues to fight will determine how quickly we get there, but the destination seems inevitable at this point.