Developing for Assistant across devices
summary
Adds voice entry points to Android apps using App Actions with over 60 built-in intents mapped to app capabilities declared in shortcuts.xml, plus inline inventories for parameter lookup. Uses the App Actions test tool in Android Studio to create a temporary backend preview so testing doesn’t require Play uploads. Wear uses health/fitness BIIs and may need extra haptics for non‑standalone apps; Android for Cars requires deep‑link fulfillment (no intents). Deep links carry BII parameters to the app.
AI-written summary · about
chapters (14)
- 0:00Assistant across devices
- 1:39App Actions and user journeys
- 3:39Voice integration architecture
- 4:20Developing for voice devices
- 4:41App functionality and intents
- 5:25Built-In Intents for devices
- 6:28Inline inventories for BIIs
- 7:54Setting up capabilities in shortcuts.xml
- 9:20Wear and Cars differences
- 10:03Fulfilling BIIs with tags
- 10:45Fulfillment for Wear and Cars
- 11:50Testing with Android Studio
- 13:16Reviewing and deploying
- 13:38Recap and next steps
related talks
15mDeveloping for Assistant across devices
27mAndroid & Assistant: a match made in heaven
40mBuilding assistive apps with App Actions
16mGoogle Assistant functionality across Android devices
16mHow to voicify your Android app
27mSession 1: Connect your Android app to Google Assistant
44mBuilding assistive apps with App Actions
21mIntegrate Google Assistant into Android for cars