iOS 27 Finally Lets Third‑Party Apps Use Google Cast – A Win for EU Users

When iOS 27 landed on our devices last week, the headline that most people skimmed over was the addition of Google Cast support for third‑party streaming apps. It might sound like a tiny checkbox in a sea of updates, but for anyone who’s ever tried to share a Netflix show from an iPhone to a non‑Apple TV, it feels like a small miracle.

Apple didn’t roll out the feature on a whim. The European Union’s Digital Markets Act (DMA) has been nudging – some would say shoving – the tech giant to open its ecosystem to rival services. In plain English, the DMA says that platforms with a lot of power can’t block developers from using competing standards, and Google Cast is the most obvious example.

So, what does the new integration actually look like? If you open a streaming app that’s updated for iOS 27 – think Hulu, Disney+, or even a niche indie movie service – you’ll now see a familiar Cast icon next to the AirPlay button. Tapping it brings up a list of nearby Chromecast‑enabled devices, just like you’d expect on Android. The catch? It works natively, without the app having to bundle its own casting SDK or jump through Apple’s proprietary hoops.

Developers got a short, tidy API in the latest Xcode release. It’s basically a wrapper around the existing MediaPlayer framework, but with a few extra calls that let the system discover and talk to Google Cast devices. Apple’s documentation even includes a side note encouraging developers to “respect user preferences” – a nod to the ongoing debate about how much control platforms should have over the user experience.

From a user perspective, the change is subtle but meaningful. You can now cast a YouTube video from the official YouTube app straight to a Chromecast dongle, then flip back to an Apple‑only app like Apple TV+ and continue watching without juggling two different “cast” buttons. The transition feels almost seamless, which is the kind of polish we’ve come to expect from Apple.

Not everyone is cheering, though. Some critics argue that Apple’s implementation is still a little too “Apple‑centric.” The Cast icon only appears after the app has opted‑in, meaning developers who haven’t updated yet won’t get the benefit. Moreover, the system still prioritises AirPlay when both options are available, a detail that could be seen as a subtle way of keeping Apple’s own ecosystem in the driver’s seat.

Apple’s own press release frames the move as “enhancing choice for users worldwide,” while also emphasizing that the feature is rolled out globally – not just in the EU. That’s a classic Apple line, but it does mean that users outside Europe get the same convenience without any extra regulatory pressure.

So, how big of a deal is this for the streaming wars? In the short term, it’s a win for consumers who own mixed‑brand home theater setups. In the longer view, it could signal that Apple is willing to bend a little under the DMA’s weight, perhaps opening the door to more interoperability down the line – think of a future where Apple’s own devices speak Spotify’s protocol as fluently as they do AirPlay.

For developers, the message is clear: update your app, or risk being left out of a growing cast‑to‑TV market. The good news? The new API is relatively lightweight, and Apple has promised extensive sample code to make the migration painless. The bad news? If you’re a small indie dev, you’ll still need to allocate resources to keep up with the rapid pace of regulatory‑driven changes.

All things considered, iOS 27’s Google Cast integration feels like a modest but welcome concession. It’s not a full‑scale opening of the walled garden, but it does let users breathe a little easier when their living room tech isn’t perfectly aligned with Apple’s own lineup. And for a platform that’s long prided itself on control, that’s a noteworthy shift.