Mobiconf 2018: Elaine Dias Batista
summary
Google introduces App Actions to predict and surface the specific action a user will take (not just the app), claiming ~60% launcher prediction and extending suggestions to smart text selection, Play Store, Assistant and Search. Integration uses actions.xml deep links for URL-template actions or schema.org structured data for content-based actions, maps built‑in intents to Android intents, and requires Play Console registration and the Actions test tool; usage reporting affects ranking. Rollout is Android‑centric and initially US English.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker intro
- 1:31The app discovery problem
- 5:49What are App Actions
- 12:15How App Actions work
- 14:51Integrating App Actions into apps
- 22:03App Actions vs Conversational Actions
- 24:52Why App Actions matter
- 26:21Getting started with Actions on Google
- 28:52Q&A session
related talks
44mBuilding assistive apps with App Actions
40mBuilding assistive apps with App Actions
35mGetting started with App Actions
16mGoogle Assistant functionality across Android devices
27mSession 1: Connect your Android app to Google Assistant
15mDeveloping for Assistant across devices
27mAndroid & Assistant: a match made in heaven
30mApp Actions