Safari on iOS: Secure but Stifling Browser Choice

By Jonathan D. Steele | November 19, 2024

Apple and the Illusion of Browser Choice

Safari might be secure and reasonably private, but there's a problem that techies have been grumbling about for years: on iOS, you're stuck with it whether you like it or not. Apple requires all browsers on iOS to use the WebKit engine—meaning that so-called alternatives like Chrome, Firefox, or Brave are essentially Safari in different clothes. It's a browser monoculture dressed up as choice. And while Apple can tout security benefits, it's time we acknowledged that this is also about control. Control that stifles innovation, limits true competition, and ultimately hurts privacy in the process.

Apple's Antitrust Troubles and the iCloud Monopoly

The issue is gaining renewed relevance as Apple faces multiple antitrust lawsuits that highlight its monopolistic practices across different verticals. The latest is a $3.75 billion lawsuit in the UK that accuses Apple of cornering the market with its iCloud service, forcing 40 million users into overpaying for storage. Apple has responded, as expected, by downplaying these claims and insisting that users have plenty of choices—they can back up their data elsewhere if they really want to, they argue. But the catch is that Apple, in many ways, does make it hard for other solutions to thrive, and iCloud is just the tip of the iceberg.

The Chokehold on iOS Browsers

The more glaring example of this monopolistic behavior is the absolute chokehold Apple has on iOS browsers. Yes, Apple was finally cornered into agreeing to allow sideloading of apps in the EU (and yes, this is actively being rolled out to comply with new regulations). But when it comes to browsers, we're still dealing with an illusion of choice. Apple mandates that all browsers on iOS—be it Chrome, Firefox, or Brave—use WebKit as their underlying engine. So if you think you're switching from Safari to Chrome for a different experience, think again; it's still Apple's code under the hood.

Legal Protection Matters: Cybersecurity incidents often have significant legal implications. Our sister firm Steele Family Law helps Illinois families navigate complex legal situations with the same commitment to protection and discretion we bring to cybersecurity.

Control vs. True Alternatives

This restriction is not about making the best product—it's about making sure Apple is the only game in town. There's a certain irony here: iOS is marketed as this walled garden where everything is optimized, safe, and consumer-friendly. But it’s precisely this control that keeps us from accessing real alternatives—alternatives that could enhance privacy, push innovation forward, and give users more power over their browsing experience. Just imagine the true versions of Firefox or Brave, unencumbered by WebKit, available on iOS. Or even a dedicated Tor browser—not the pseudo-VPN setup with Orbot, but a true Tor experience, bringing advanced privacy to iPhones everywhere.

Security Arguments and the Case for Choice

Apple’s narrative has always been about putting user privacy and security first. And while there is merit to the argument that keeping all browsers under the WebKit umbrella reduces the attack surface, there are other ways to mitigate those risks. For instance, Apple could maintain strict App Store guidelines, require transparency about browser security measures, and yes, provide prominent disclaimers if needed. The key difference would be offering users a choice—the kind of choice that empowers them to decide what matters most: security vetted by Apple or enhanced privacy and features offered by other engines.

Stripped-Down Alternatives

As it stands, even the big players like Brave are just stripped-down versions of what they could be. Brave’s famed ad-blocking capabilities? Watered down. Firefox’s privacy-first ethos? Constrained. None of these alternatives are truly alternatives, because they're all shackled to the same WebKit engine.

The Need for Real Browser Competition

The EU forced Apple to open up sideloading, and it's a step in the right direction. But why isn't Apple facing more heat over the WebKit requirement for browsers on iOS? It's time for regulators, consumers, and yes, the tech press, to demand real browser competition on iOS—not just an illusion. Removing the death grip of WebKit would do more than just offer diversity; it would drive innovation, bolster privacy options, and ultimately create a better browsing experience for everyone.

True Privacy Requires Real Choice

Apple needs to understand that privacy, real privacy, isn’t about locking everyone into your version of the safest box—it’s about empowering users to make their own informed choices. And right now, we simply don’t have that on iOS. Let’s change that.

---

Related Articles

Your Security is Non-Negotiable

At SteeleFortress, we've protected hundreds of organizations from cyber threats.

Schedule Your Free Security Assessment →

Stop hoping you won't get breached.

Get the 15-point Security Audit Checklist that attackers don't want you to have. Plus weekly intel briefs - no fluff, no vendor pitches.

No spam. Unsubscribe anytime. We don't sell your data - we protect it.