Google integrates Assistant with dedicated assistive devices through a partnership with Tobii Dynavox and makes Action Blocks more accessible
Context & Ripple Effects
This closes a loop Google opened a year earlier: Action Blocks was announced in late 2019 as a way to turn multi-step Assistant routines into single-tap buttons, then shipped broadly in May's Android accessibility rollout. The Tobii Dynavox partnership is the next step — instead of living only on Android phones, the same button-plus-Assistant model is being embedded into dedicated assistive hardware.
It also extends a distribution pattern Google has run since the 2017 Assistant SDK and the GE appliance deal: licensing Assistant into third-party devices rather than confining it to Pixel and Nest hardware. Tobii Dynavox makes communication devices for users with speech and motor impairments, so this puts Assistant on screens its owners cannot easily operate by touch.
First-order effects
- Tobii Dynavox's assistive devices gain native Assistant voice control, letting their users trigger routines and smart-home actions without picking up a separate phone.
- The Action Blocks updates lower the setup burden for users with cognitive or motor disabilities, making the customized-button workflow usable by more of its intended audience.
Second-order effects
- Rival assistive-technology vendors now face pressure to strike similar assistant integrations or explain why their devices lack voice control that a competitor ships by default.
- For Google, each dedicated-device deal widens Assistant's footprint beyond phones and speakers at near-zero incremental cost, echoing the appliance-partner playbook used with GE.
Third-order effects
- If the pattern holds, voice assistants consolidate into an accessibility layer across device classes — the interface of record for users touchscreens exclude, not just a convenience feature on consumer gadgets.
The trend: Voice assistants are expanding from consumer phones and speakers into specialized assistive hardware, with Google reusing its SDK-era partner-integration playbook to reach users its own devices don't serve.