Android & Assistant: a match made in heaven
summary
Android reaches 2.5 billion monthly users and Google Assistant recently quadruples to over a billion devices, and app actions let an installed app surface via voice by matching built‑in intents to an actions.xml mapping in res/xml; deep links use Android Studio’s App Links Assistant, slices require a SliceProvider and the Slice Viewer ADB tool, and fulfillment can launch activities or return UI. Developer preview is US English only, one built‑in intent is broadly available now, testing uses the app actions test plugin, and onProvideAssistContent plus Firebase App Indexing improve visibility.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:19What are app actions
- 5:52Why use app actions
- 9:27Developer preview limits
- 13:25App architecture needs
- 14:27Building deep links
- 17:21Using slices
- 19:10Configuring actions.xml
- 21:16Optimizing for Assistant
- 23:23Testing and deploying
- 26:11Summary and Q&A
related talks
15mDeveloping for Assistant across devices
15mDeveloping for Assistant across devices
27mGoogle Assistant for Android developers
27mSession 1: Connect your Android app to Google Assistant
16mGoogle Assistant functionality across Android devices
24mDemystifying the Google Assistant for Android developers
44mBuilding assistive apps with App Actions
40mBuilding assistive apps with App Actions
