Apple is preparing to dismantle one of its most tightly controlled system-level features: AirPlay. According to Bloomberg’s Mark Gurman, iOS 27 will let users replace AirPlay with third-party streaming protocols at the operating system level—a move clearly aimed at satisfying the European Union’s Digital Markets Act (DMA). That’s not just a tweak. It’s a direct hit to Apple’s longstanding gatekeeping over how media flows from iPhone to TV. And it’s happening on May 24, 2026, because the clock’s ticking on EU enforcement.
Key Takeaways
- Apple is developing system-level support for third-party streaming protocols in iOS 27, allowing users to set alternatives like Google Cast as default.
- The change is a response to the EU’s Digital Markets Act, which classifies Apple as a gatekeeper and mandates interoperability.
- Google Cast is expected to be the most widely adopted alternative, but any manufacturer could build native iOS integration without relying on AirPlay or Bluetooth.
- The feature will likely launch in the European Union only—other regions shouldn’t expect it anytime soon.
- This marks a rare crack in Apple’s end-to-end ecosystem, where even minor third-party access has historically been blocked or neutered.
third-party streaming protocols Break Apple’s AirPlay Lock
You tap “Share” on a video in Safari. You see a little icon. You expect it to work. But in half the hotels across Europe, that icon either doesn’t appear or fails silently because the TV only supports Google Cast. That’s been the iOS user experience for years—frustrating, inconsistent, and entirely by design. AirPlay was never just a protocol. It was a moat.
AirPlay launched in 2010 as AirTunes, a way to wirelessly stream music to a single device: the AirPort Express. It was a niche feature for Apple loyalists. But by 2011, it evolved into AirPlay, enabling video mirroring and streaming to Apple TV. From there, it became the default path for any media leaving an iOS device. No other standard was given equal footing. No competing protocol could register at the system level. Even when Miracast emerged as a wireless display standard on Android, Apple ignored it. Bluetooth was used for audio, but never video. The message was clear: if you wanted smooth casting on iPhone, you played by Apple’s rules.
But iOS 27 could change that. According to Gurman’s Power On newsletter, Apple is building the ability to replace AirPlay with other streaming standards directly in the OS. That’s not about adding another app. It’s about letting Google Cast, or something else, sit at the same level as AirPlay in Control Center, notifications, and system APIs. You’ll be able to set it as default. You won’t need to open the YouTube app to cast. It’ll just work—like it should have years ago.
And make no mistake: this isn’t voluntary. Apple didn’t wake up one morning and decide to get interoperable. The EU’s DMA explicitly prohibits gatekeepers from favoring their own services in system-level functions. Since AirPlay is baked into iOS as the sole native casting method, it qualifies. Apple has no choice but to open it—or face fines up to 10% of global revenue.
The DMA’s Article 6(f) is the specific clause forcing this change. It states that gatekeepers must allow “interoperability of ancillary services” and cannot prevent business users or end users from using, selling, or accessing services via third-party apps. Streaming is no longer seen as an optional add-on. It’s a core functionality. And with Apple controlling the only native path, regulators see it as anti-competitive. The May 24, 2026 deadline isn’t arbitrary—it’s when Apple must fully comply with all DMA obligations or risk penalties that could hit €20 billion.
Why Google Cast Stands to Win Most
Of all the potential beneficiaries, Google Cast is the obvious big winner. It’s already built into millions of smart TVs, soundbars, and streaming sticks across Europe. Chromecast devices are cheap, widely adopted, and deeply integrated into Google’s ecosystem. But until now, iOS support has been spotty—limited to apps that bundle the Cast SDK. There’s no system-level hook. No unified interface. No default option.
That’s about to change—if you’re in the EU. With native integration, Google Cast could finally behave like a first-class citizen on iPhone. You’ll cast from Photos, Safari, or third-party apps without needing the Google Home app running in the background. The experience will be smoother, more consistent, and far less janky. And because it’s set as default, even apps that don’t explicitly support Cast could route through it via the system layer.
Google Cast’s architecture has always been lightweight. It doesn’t require the sending device to handle the stream directly. Instead, the iPhone sends a command to the receiving device—“play this URL”—and the TV fetches the content itself. That reduces battery drain and avoids compression issues. AirPlay, by contrast, often transcodes video on the sending device, which can lead to lag and overheating. With system-level Cast, iOS devices could offload more work to the display, improving reliability.
There’s also a network benefit. AirPlay relies on mDNS (multicast DNS) for discovery, which doesn’t always traverse subnets or corporate firewalls. Google Cast uses a mix of local network scanning and cloud signaling, making it more resilient in complex environments like hotels, offices, or university dorms. For users, that means fewer “device not found” errors. For developers, it means more predictable behavior across networks.
It’s Not Just Google—It’s Any Manufacturer
Google may be the headliner, but the implications go further. The DMA doesn’t care which third party benefits. It only demands that alternatives get fair access. That opens the door for Sonos, Roku, or even niche smart display makers to build their own system-level streaming handlers. They won’t need to license AirPlay. They won’t need to rely on Bluetooth, which is unreliable for video. They can offer full iOS integration—same as AirPlay—through a certified protocol.
The certification process will likely mirror what Apple did for alternative app stores in iOS 17.5. Developers will need to meet security standards, submit their protocols for review, and ensure they don’t compromise privacy. But once approved, their service could appear in Control Center alongside AirPlay, with no technical limitations. The protocol doesn’t need to be open-source, but it must be documented and available for licensing on fair terms.
Imagine a hotel chain deploying in-room speakers that work smoothly with any guest’s iPhone, regardless of whether they own Apple hardware. Or a car manufacturer building native iPhone video routing into its infotainment system without Apple’s approval. That’s the kind of interoperability the EU wants. And for the first time, Apple’s ecosystem is being forced to allow it.
Hardware makers have long complained about AirPlay’s licensing costs and technical constraints. Apple charges manufacturers a fee to include AirPlay support, and the certification process can take months. Now, those companies can bypass Apple entirely. They might even develop proprietary protocols optimized for their own devices—say, a smart mirror that streams health metrics from an iPhone workout app, or a kitchen display that pulls recipes from iOS notes. The bottleneck was never technical. It was permission.
The EU-Only Rule Is the Real Story
Here’s what’s not being said outright in the report but is glaringly obvious: this feature will almost certainly be geofenced to the EU. Apple has already done this with alternative app marketplaces in iOS 17.5. It rolled out the App Store changes only in Europe. The same logic applies here. If Apple can limit DMA compliance to the smallest possible footprint, it will.
Which means if you’re in the U.S. Canada, Japan, or Australia, you won’t see native Google Cast integration in iOS 27. You’ll still be stuck with AirPlay as the only system-level option. Apple won’t break its own ecosystem globally just because Europe demands fairness. That’s cynical, but predictable. It’s also a reminder that regulatory pressure—not user demand or innovation—is what finally cracks Apple’s control.
There’s precedent. When the EU forced Apple to adopt USB-C by 2024, the company did it—but only for new iPhones. The Lightning port disappeared in Europe, but Apple continued selling Lightning accessories elsewhere. Similarly, iOS 17.5 introduced browser engine choice in the EU, but Safari remains the only option with full WebKit access outside it. Apple’s strategy is clear: comply where required, maintain control everywhere else.
- iOS 27 is expected to launch fall 2026, with DMA-compliant features active in EU regions only.
- Apple’s AirPlay has been the exclusive native casting protocol on iOS since 2010.
- The DMA fines for noncompliance can reach €20 billion or 10% of global turnover.
- Google Cast launched in 2013 and is now supported on over 200 million devices worldwide.
- Apple introduced alternative app store distribution in the EU with iOS 17.5 in March 2025.
What This Means For You
For developers, this shift opens a new vector for system-level integration. If you’re building a streaming protocol or hardware product, you can now design for iOS without needing Apple’s blessing. You’ll need to comply with Apple’s certification and security requirements, but the door is open. The APIs will exist. The hooks will be there. And because it’s a system-level feature, your protocol won’t be buried in app settings—it could be the default.
Scenario one: You’re a startup making smart home displays for elderly users. Previously, you had to rely on AirPlay or push users to download your app. Now, you can build a certified protocol that lets family members cast photos, videos, or telehealth calls directly from their iPhones. No app needed. Setup happens over NFC or QR code. The device appears in Control Center like any other. Adoption jumps because it just works.
Scenario two: You’re a developer at a car company rolling out a new infotainment system. Until now, Apple CarPlay was the only smooth way to get iPhone content on screen. But CarPlay is limited—Apple controls the UI, restricts background apps, and charges OEMs for integration. With the new iOS 27 changes, your team builds a native video routing protocol. It handles navigation, video calls, and media without CarPlay. Users choose it as their default streamer. You gain control. Apple loses a chokehold.
Scenario three: You run a hotel chain with 50,000 rooms across Europe. Guests constantly complain about not being able to cast from their phones. You install TVs with Google Cast, but it only works from Android or inside specific apps. With iOS 27, that changes. Guests can cast from any app, any tab, any photo. Support tickets drop. Satisfaction rises. The feature pays for itself in six months.
For founders and product teams, this is a signal that regulatory pressure can force access to even the most closed ecosystems. If you’ve been locked out of iOS integration because Apple favors its own stack, the EU’s DMA might be your backdoor. Build for Europe first. Certify your protocol. Use the new iOS 27 hooks. And don’t assume Apple’s global policies are permanent—especially when money and compliance are on the line.
What Happens Next
The May 24, 2026 deadline is firm. Apple will have to demonstrate compliance to the European Commission. That means not just shipping the feature, but proving it’s functional, discoverable, and not sabotaged by poor performance or confusing UX. The Commission has already signaled it will scrutinize “dark patterns” or design choices that steer users back to AirPlay.
Will Apple appeal? Unlikely. The company fought the App Store changes but ultimately complied. The risk of daily fines and frozen revenue is too high. Instead, expect minimal, literal compliance: the feature will exist, but Apple will do everything it can to make AirPlay feel faster, more reliable, or better integrated. Maybe third-party protocols get slower discovery times. Maybe they’re buried in a submenu unless manually promoted.
And what about the rest of the world? If the U.S. Congress passes legislation similar to the DMA, Apple might expand the feature. But without legal pressure, it won’t. The company’s business model depends on control. Every crack in the wall invites more. Apple knows that once a feature exists in one region, users elsewhere will demand it. Journalists will highlight the disparity. Competitors will call it unfair. The pressure builds.
Will this be the start of broader interoperability? Maybe. But only if regulators keep pushing. This isn’t about user choice. It’s about legal survival. And for now, that survival is confined to Europe.
Will Apple ever bring third-party streaming protocols to the rest of the world? Or will we accept that fair competition only exists where regulators force it? The answer might define the next decade of tech platform control.
Sources: 9to5Mac, original report
