Apple is preparing to let iOS users choose Google Cast as a default streaming protocol in iOS 27—but only if they’re in the European Union. That’s the clear takeaway from a May 25, 2026 report by 9to5Google, which cites Bloomberg’s latest on Apple’s compliance efforts under the Digital Markets Act (DMA). This would mark the first time Apple opens up its tightly controlled AirPlay ecosystem to a named third-party alternative. And while that sounds like progress, it’s progress with borders. Google Cast integration won’t be a global feature. It’ll be a legal concession—one carved out specifically for Europe.
Key Takeaways
- Apple is testing native Google Cast integration in iOS 27, allowing users to set it as a default streaming option.
- The move is driven by the EU’s Digital Markets Act, not user demand or product vision.
- Third-party casting will likely be restricted to the EU, mirroring Apple’s past behavior with DMA-mandated changes.
- Developers currently must build Google Cast support app-by-app; iOS-level integration would reduce that burden—for some.
- Apple still doesn’t support AirPlay on Android, and there’s no sign that’ll change—even with EU pressure.
Google Cast Integration Isn’t a Feature—It’s a Compliance Patch
Let’s call this what it is: Apple isn’t adding Google Cast because it wants to. It’s doing it because the European Commission said it has to. The DMA’s interoperability rules now require gatekeepers like Apple to open their proprietary systems when they control a bottleneck. AirPlay is one of those bottlenecks. It’s the only native streaming protocol on iOS, and it only works smoothly with Apple-certified hardware. That gives Apple outsized control over how video, audio, and photos move from iPhones to TVs and speakers—even when users own third-party devices.
There’s been no shortage of workarounds. Developers can embed Google Cast into their apps. Spotify does it. YouTube does it. But that means the feature only works inside those apps. You can’t, for instance, long-press a video in Safari and send it to your Chromecast. You can’t swipe up from the lock screen and cast a song playing in Apple Music to a Nest Hub. Without system-level support, casting remains fragmented and incomplete.
Now, Apple is building in the ability to set third-party protocols as defaults. Google Cast is named in the report as one of those options. But don’t mistake this for openness. It’s containment. The company has done this before. USB-C charging, alternative app stores, and web browser engine changes were all rolled out strictly within EU borders. There’s no reason to expect this time will be different.
Why Google Cast—and Not Miracast or Others?
Of all the third-party protocols out there, Google Cast is the only one Bloomberg’s report specifically names. That’s telling. It’s not because Cast is technically superior—its latency can be spotty, and it relies heavily on cloud relays. It’s because Cast has the widest consumer footprint. According to Google, over 200 million Chromecast-enabled devices were in use by 2025. That includes smart TVs from Sony, Philips, and TCL, as well as speakers from JBL, Bose, and Lenovo. It’s the de facto standard for non-Apple households.
Miracast? It’s barely alive. Wi-Fi Alliance data from 2025 shows declining certification rates, and most Android OEMs have quietly dropped it in favor of Google Cast or proprietary solutions. Samsung still supports it, but mostly for legacy compatibility. DLNA? That’s a relic. Apple isn’t going to spend engineering cycles on protocols with negligible user bases. If they’re going to open the gate, they’ll do it for the one that matters: Google’s.
What This Means for Developers
If you’re building an iOS app that streams media, Google Cast integration currently means maintaining a separate SDK, handling authentication flows, and dealing with inconsistent behavior across iOS versions. It’s not terrible—but it’s not trivial, either. With system-level support, some of that lifts. The OS would handle device discovery, connection management, and maybe even background casting. That’s a win.
But—and it’s a big but—this only helps if your users are in the EU. Everyone else still gets the old, app-by-app model. That means you’re either maintaining two codepaths, or you’re optimizing for one market over others. And Apple won’t make this easy. Remember how the App Tracking Transparency framework was rolled out? With minimal documentation and last-minute API changes. Expect similar friction here.
The EU Gets Choice. The Rest of Us Get Apple’s Way.
It’s not lost on anyone that Apple’s compliance moves are geofenced. The company doesn’t like being told what to do. And it’s made that clear through its rollout patterns. Take the alternative app store rules: only available in the EU. Web apps that bypass the App Store? Only in the EU. Even the new web distribution model for games—announced in 2025—was limited to Europe.
So why would streaming be any different? Apple has spent years building AirPlay into everything—HomePod, Apple TV, even third-party accessories via its MFi program. It’s a revenue stream, not just a feature. Opening it globally would undermine that ecosystem. Limiting Google Cast integration to the EU lets Apple comply without cannibalizing its business.
And let’s be honest: outside the EU, there’s no regulatory hammer forcing Apple’s hand. The U.S. has no equivalent to the DMA. China protects its own tech giants. Other markets either lack enforcement power or haven’t prioritized interoperability. So Apple wins by doing the bare minimum.
A One-Way Street: AirPlay Still Won’t Come to Android
Here’s the irony: while iOS users in Europe may soon cast to Chromecast by default, Android users still can’t do the reverse. Apple hasn’t made AirPlay available on Android, and there’s zero indication it ever will. You can’t install an AirPlay receiver on your Samsung phone. You can’t mirror your iPhone screen to an Android tablet using a native app. That asymmetry isn’t accidental. It’s policy.
Apple’s entire ecosystem strategy relies on frictionless in-family experiences and high switching costs. Letting AirPlay work on Android would reduce that friction. It would make mixed-device households easier. And that’s the last thing Apple wants. Even if the EU tried to mandate it—which it hasn’t—Apple would fight it. The company has already argued that AirPlay is a “security-critical service” and that opening it to non-Apple platforms would create vulnerabilities. It’s a convenient argument. Whether it’s true is another matter.
- Google Cast integration in iOS 27 will likely be limited to EU users.
- Developers must still support casting manually in non-EU regions.
- AirPlay remains iOS- and macOS-only; no Android support in sight.
- Apple’s compliance strategy is consistently regional, not global.
- The change reflects regulatory pressure, not product evolution.
What This Means For You
If you’re a developer, start planning for fragmentation. In the EU, you might be able to de-prioritize in-app casting UIs and rely on system-level hooks. But elsewhere, you’ll still need to bundle the Cast SDK and manage connections yourself. That means divergent feature sets across regions. It also means testing on EU-configured devices to ensure your app doesn’t break when system casting is active. Apple will likely expose new APIs around default streaming handlers—watch for them at WWDC 2026 in June.
For founders and product leads, this is a reminder: platform policy is now geopolitical. Your app’s functionality depends not just on iOS version, but on where your user lives. That complicates design, support, and marketing. If you’re building a media app with global ambitions, you can’t assume a uniform experience. Apple has made that clear. The EU is the exception, not the rule.
And here’s the real question: if Apple can integrate Google Cast for the EU, what stops them from doing it everywhere else? Nothing—except profit. This isn’t a technical limitation. It’s a business one. So the answer isn’t in code. It’s in regulation. Will other regions follow the EU’s lead? Or will we accept that basic interoperability is a luxury, not a right?
Sources: 9to5Google, Bloomberg
