Google Assistant for Android Developers

Cb3c988ada1925dbb88a2b1f11c60f3f?s=47 elainedb
February 22, 2019

Google Assistant for Android Developers

Google Slides (with animations): https://docs.google.com/presentation/d/1XwcTr_btkZJdXO1B_1L6z1xIfURzI58MixTTGDJyOa0

The fact that "apps" for the Google Assistant and for Android are both available on Android smartphones can be the cause of some confusion. Do I have to go to the Play Store to download and install an "app" for the Google Assistant? Can I launch a Google Assistant experience from an Android app? How to integrate advanced voice recognition (NLP or other) on existing apps? What experience should I offer on my app? In this talk I will answer these questions, do a comparison of the ecosystems and how they can work together.

Cb3c988ada1925dbb88a2b1f11c60f3f?s=128

elainedb

February 22, 2019
Tweet

Transcript

  1. 3.

    @elainedbatista @elainedbatista Outline 1. Assistant vs. Android a. Devices b.

    UI c. Development d. Distribution 2. Mixing both a. App Actions b. Google Maps / Chrome c. Android app from Assistant d. Action from Android app 3. Integrating "Google Assistant"-like features into Android apps 4. Final thoughts 3
  2. 8.

    @elainedbatista 1. Devices - Conclusion ➔ Android is an Operating

    System capable of running the Google Assistant ◆ and you can launch it fairly easily on it ➔ The Google Assistant is a piece of software that works on a bunch of OSs ◆ Android / iOS ◆ Chrome OS, KaiOS ◆ … and others
  3. 14.

    @elainedbatista 3. Development Actions on Google - Node.js / Java

    (Kotlin) official libraries - Conversation API (REST calls) - Dialogflow - Google Assistant SDK Android SDK - Java / Kotlin - JS, Flutter, Xamarin...
  4. 19.

    @elainedbatista @elainedbatista Mixing the two platforms 1. App Actions 2.

    The Google Maps / Chrome cases 3. Calling an Android app from the Assistant 4. Calling an Action from and Android app 19
  5. 20.

    @elainedbatista @elainedbatista Mixing the two platforms 1. App Actions 2.

    The Google Maps / Chrome cases 3. Calling an Android app from the Assistant 4. Calling an Action from and Android app 20
  6. 23.

    @elainedbatista App Actions - Play Store ➔ Installed apps ◆

    Deep-link into it ➔ Not installed apps ◆ Open details page ◆ Deep-link after installation 23
  7. 24.

    @elainedbatista App Actions ➔ Users don't want to simply "open"

    an app, they want to get something done ➔ App Actions are a new way of re-engaging with your users in the right context at the right moment ➔ Based on Actions on Google's Built-in Intents 24
  8. 26.

    @elainedbatista @elainedbatista Mixing the two platforms 1. App Actions 2.

    The Google Maps / Chrome cases 3. Calling an Android app from the Assistant 4. Calling an Action from and Android app 26
  9. 28.

    @elainedbatista @elainedbatista Mixing the two platforms 1. App Actions 2.

    The Google Maps / Chrome cases 3. Calling an Android app from the Assistant 4. Calling an Action from and Android app 28
  10. 30.

    @elainedbatista @elainedbatista Mixing the two platforms 1. App Actions 2.

    The Google Maps / Chrome cases 3. Calling an Android app from the Assistant 4. Calling an Action from and Android app 30
  11. 36.

    @elainedbatista Integrating conversational features 1. Hot-word detection ◆ Android API

    - AlwaysOnHotwordDetector ◆ Voice actions / Voice interaction API ◆ Porcupine / Snowboy / Snips / PocketSphinx 2. NLP/NLU SDK for mobile ◆ From Google: Dialogflow, ML Kit, TensorFlow, Cloud APIs ◆ Amazon Lex ◆ RASA NLU, Snips, PyTorch and much more... 36
  12. 39.

    @elainedbatista Final thoughts ➔ Don't try to simply port all

    the features from your current app into the Assistant ◆ Think about the appropriate use cases - start with 1 or 2 ◆ They have to make sense as a conversation ➔ Integrating features into an existing mobile app is a great way to get your users accustomed to this new technology 39
  13. 40.

    @elainedbatista Final thoughts ➔ If you already have an app:

    ◆ Develop 1 or 2 features for the Assistant (if they make sense) and see how it goes - it's a new channel that your users are on ➔ If you don't have an app yet: ◆ Try both approaches (app, action) - you can even make a "voice first" mobile app experience 40