Apple appears to be preparing a small but meaningful change to how iPhones beam media to speakers and TVs: system-level support for third-party streaming protocols such as Google Cast (Chromecast). The change, reported by Bloomberg and relayed across tech outlets, would let alternatives to AirPlay be installed and even set as the default on iOS — most likely as part of iOS 27 and most likely to satisfy the European Union’s Digital Markets Act.
A reluctant concession
If true, this is less a sudden embrace of Google’s ecosystem and more a tactical move. AirPlay has been Apple’s exclusive, tightly integrated method for sending audio, video and photos from an iPhone to a compatible TV or speaker. Other protocols — Google Cast chief among them — have worked in individual apps when developers choose to add them, but they’ve never been first-class citizens inside iOS itself.
Mark Gurman’s reporting suggests Apple will build hooks into iOS 27 that let third-party casting frameworks plug into the system in the same way AirPlay does today. That means an app wouldn’t need bespoke code to find and talk to a Chromecast-equipped TV; iOS could surface Cast devices in the same interface that currently lists AirPlay receivers. Users could pick a non‑Apple option as the default for "casting" media off the phone.
Why now? The EU’s Digital Markets Act has forced big platform owners to make their systems more open to rivals. Apple’s response over the past couple of years has been cautious and piecemeal — enabling some EU-specific features while keeping the rest of the world on the status quo. This rumored change looks like another example of Apple picking its battles: meet the regulator’s letter without fully reinventing iOS globally.
What it might look like in practice
Details remain scarce. The report says third-party protocols would be able to register with iOS at a system level so the OS can offer them as options when you want to beam content. That could simplify things for users in mixed-device homes (Android phones and iPhones live together) and for travelers who encounter Chromecast-only hotel rooms.
But the integration likely won’t be identical to AirPlay in every way. Apple could gate which APIs are exposed, require security checks, or put limits on how deeply a rival protocol can interact with system services. The company has repeatedly raised concerns about potential security and privacy implications when opening system hooks to outsiders — concerns it voiced during earlier DMA-driven shifts like alternative app marketplaces and sideloading. If you’ve been following the iOS beta cycle, some EU-facing changes have already crept in; see how recent builds began testing accessory and messaging tweaks in the iOS 26.5 developer releases iOS 26.5 developer beta arrives — no Siri, but Maps, RCS and EU accessory changes creep in.
EU-only or global roll‑out?
Apple’s history suggests the safest bet is that any Cast integration will debut in the EU and may remain region-locked. The company has repeatedly implemented DMA-driven features only in European builds rather than adopting them worldwide. That said, maintaining two divergent code paths can be costly. For some features Apple has ultimately shipped them globally when the engineering lift was low; for others it’s kept the split. Whether Google Cast ends up on iPhones everywhere may come down to how complex the integration turns out to be.
Bigger picture: iOS 27 isn’t just about casting
This rumored change sits alongside a larger set of iOS 27 experiments and concessions. Apple is widely reported to be leaning into AI upgrades (from smarter image models to a rethink of Siri) and testing broader changes to camera and Photos, while also building infrastructure to support third-party apps and sideloading where regulators demand it. If you want a sense of the bigger roadmap and the tensions Apple is juggling, look into earlier leaks about iOS 27’s camera and Siri ambitions iOS 27 leaks point to a truly customizable Camera and a ChatGPT-like Siri and the company’s plans around AI extensions and stability iOS 27: Apple’s stability reset and the smart‑phone AI marketplace.
Why it matters beyond convenience
At first blush, adding Google Cast as a native option is mostly a convenience win: fewer app-level headaches, less fiddling when you walk into a Chromecast‑only room, and smoother multi-device homes. But it also recalibrates a small corner of platform control. Allowing a competing streaming protocol into the system UI weakens the exclusivity AirPlay has enjoyed, at least in territory where regulators press the point. For device makers and service providers who have avoided AirPlay licensing, it could mean less friction integrating with iPhones.
That’s precisely why Apple will be careful. The company sells an experience as much as hardware — and that experience includes how easily your iPhone talks to displays and speakers. Any change will be weighed against brand and security concerns.
Imagine a hotel TV that only lists Chromecast by name when you try to beam a movie from your phone — and then imagine it listing both Cast and AirPlay and letting you pick a default. Small adjustment, big implications for how ecosystems co-exist.
No official announcement is scheduled, but WWDC is near and iOS 27 is expected to be a focal point. Whether Google Cast on iPhones becomes a widely available convenience or a regionally contained footnote will tell us a lot about how Apple plans to navigate regulators, competition and customer experience going forward.
