Building assistive apps with App Actions
summary
Google moves from suggesting 5 apps with a 60% prediction rate to suggesting specific in-app tasks by mapping semantic intents to app entry points. Developers add an actions.xml deep links file and support deep link intent filters, or surface content via schema.org markup on the website; Android Studio’s Action Test Tool previews behavior and Play Console registers the action for system suggestions on launcher, smart text selection, Play Store, Assistant and Search. The feature sits in developer preview (not yet public).
AI-written summary · about
chapters (23)
- 0:00Intro
- 4:53Apps are great
- 5:51Users abandon apps
- 6:59New apps
- 9:17Regression
- 10:02Predictive A Probe
- 11:42Content Based Action
- 12:51Android
- 15:58Play Store
- 17:32Google Assistance
- 17:59Google Search
- 18:35Routine Intents
- 20:20Activity Intents
- 21:36Integration
- 24:02URL Templates
- 29:13Action Test Tool
- 30:08Actions of Google
- 31:38Summary
- 33:07App Actions Android
- 33:41Google Assistant Android
- 35:46Google Assistant Developer Preview
- 37:42Google IO
- 38:11Questions
related talks
40mBuilding assistive apps with App Actions
35mGetting started with App Actions
15mDeveloping for Assistant across devices
37mMobiconf 2018: Elaine Dias Batista
27mAndroid & Assistant: a match made in heaven
03mApp Actions test tool
30mApp Actions
35mExtend an Android app to Google Assistant with App Actions