Google to replace its “Works with Nest” program this summer with “Works with Google Assistant”, which would give vetted partners access to customer data
As Google is further integrating the Nest brand, it is also introducing some significant changes to the way Nest products will work.
Context & Ripple Effects
The move completes an arc that started when Alphabet pulled Nest back under Google in February 2018, putting CEO Marwan Fawaz under hardware chief Rick Osterloh — a reorg that signaled Nest would stop running as a semi-independent subsidiary. The new program is the API-side consequence: instead of a standalone Nest developer ecosystem, integrations route through Google Assistant, where vetted partners get access to customer data.
First-order effects
- Existing Works with Nest partners must re-qualify under the Assistant program's data-sharing terms or lose their integrations; after pushback, Google clarified that existing connections keep working beyond the Aug. 31 cutoff until they are replicated in the new program.
Second-order effects
- Smart home device makers now face a fork: accept Google's data-access terms for Assistant compatibility or drop out — the dynamic behind The Verge's reporting that the switch could shrink the pool of compatible devices, while Amazon gets an opening to court partners who balk at the data terms.
Third-order effects
- If the pattern holds, smart home interoperability stops being an open-API norm and becomes a privilege granted by whichever assistant platform controls the data layer — consumers who wanted a privacy fence around their homes get a walled garden instead, and regulators gain a concrete case study in platform gatekeeping over consumer data.
The trend: Voice assistants are consolidating into the operating layer of the smart home, with each platform's data-access terms — not open standards — deciding which devices stay compatible.