Sonos says it is delaying support for Google Assistant, announced in 2017 and slated for the Sonos One in 2018, until 2019
Micah Singleton / The Verge :
Context & Ripple Effects
When Sonos launched the Alexa-powered Sonos One at $199 in October 2017, the pitch was a speaker that would eventually carry both assistants, with Google Assistant and AirPlay 2 promised for the following year. CEO Patrick Spence reaffirmed that timeline in a June 2018 interview, saying Assistant was still coming while flagging an expanded "Works with Sonos" program.
This delay pushes that promise past its original window, but the arc resolves: a private beta begins in January 2019, and by May the feature ships to the Sonos One and Beam through a software update. The longer story is rockier — the partnership later curdled into litigation, with the US ITC ruling in Sonos' favor and Google changing how Assistant device setup works.
First-order effects
- Sonos One buyers who chose the speaker partly on its dual-assistant pitch are stuck with Alexa as the only built-in voice option for months longer than promised.
- Sonos must keep defending a 2017 commitment it can't control the timing of, since Assistant integration depends on Google's own development schedule, not just its hardware.
Second-order effects
- Google's slow pace hands Amazon a longer exclusive window on the most credible third-party smart speaker, reinforcing Alexa's default position in the home-audio segment.
- Sonos leans harder on its other platform bets — AirPlay 2 and the "Works with Sonos" expansion Spence outlined — to hedge against any single assistant partner setting its roadmap.
Third-order effects
- If multi-assistant hardware keeps shipping on the platform partner's clock rather than the manufacturer's, voice-assistant support becomes a dependency risk rather than a differentiator — a dynamic that eventually surfaced openly in the Sonos-Google patent fight and the ITC ruling that forced Google to rework Assistant device setup.
- Speaker makers may respond by designing hardware around open or swappable assistant layers instead of betting launch marketing on a second assistant they don't control.
The trend: Smart-speaker makers are learning that multi-assistant promises are only as reliable as the platform partners who control the software, making voice-assistant support a dependency to be managed rather than a feature to be announced.