Google's Home Hub doesn't run Android Things, the platform Google purposely built for IoT products like smart displays, but uses Google's Cast platform instead
Google built a platform for smart displays and then didn't use it in the Home Hub. — On Tuesday, Google announced the Google Home Hub …
Context & Ripple Effects
Android Things began life as Brillo, the stripped-down OS meant to anchor Google's smart-home ecosystem from the first OnHub router onward, and Home Hub was exactly the kind of device it was built for. Instead, Google launched its smart display on Cast — the streaming protocol it had already turned into a walled garden by barring vendors from adding Alexa if they wanted continued Cast access.
The choice reads as a verdict on Google's own IoT platform strategy: rather than betting its flagship display on Android Things, Google doubled down on the Cast-plus-Home-app stack it had been rebranding and consolidating since 2016. The eventual shutdown of Android Things entirely retroactively confirms which bet won.
First-order effects
- Android Things loses its highest-profile prospective customer on day one — Google's own hardware team chose Cast over the platform built for this product category.
- Home Hub ships as a Cast endpoint, meaning its capabilities are bounded by what Google streams to it rather than what a local Android build could run.
Second-order effects
- Hardware partners eyeing smart displays now have a clear signal that Cast is Google's supported path, deepening the existing lock-in where Cast access already excludes rival assistants like Alexa.
- Any vendor that invested in Android Things for displays or speakers faces a shrinking ecosystem, a squeeze that ends with Google announcing the platform's shutdown.
Third-order effects
- Google's smart-home hardware strategy consolidates around a single controlled stack — Cast protocol, Home app, Assistant — at the expense of an open-ish Android derivative, and the leaked Nest Hub Max follow-up shows the display line continuing on that same foundation.
- The pattern points toward big-platform IoT strategies favoring proprietary runtime layers over general-purpose mobile OS derivatives, leaving partner-built ecosystems dependent on whichever stack the platform owner happens to be pushing.
The trend: Smart-home platforms are consolidating around tightly controlled proprietary stacks, with Google phasing out open Android derivatives like Android Things in favor of Cast and its own assistant surface.