[FEF] Voice: The New Frontend

[FEF] Voice: The New Frontend

B36609b33707f04623f84f7381d5e94e?s=128

Nara Kasbergen

April 03, 2019
Tweet

Transcript

  1. 2.
  2. 3.
  3. 5.
  4. 6.

    Vision of the future How we got here Where we

    are today How to build for voice today Lessons learned AMA (Ask Me Anything)
  5. 7.
  6. 8.
  7. 9.
  8. 10.
  9. 11.
  10. 12.
  11. 13.
  12. 14.

    definition: the ability of a computer program to understand human

    language as it is spoken. NLP is a component of artificial intelligence (AI). (source) circa 1960 first major advances in the 1980s
  13. 15.

    definition: Machine learning is an application of artificial intelligence (AI)

    that provides systems the ability to automatically learn and improve from experience without being explicitly programmed. Machine learning focuses on the development of computer programs that can access data and use it to learn for themselves. (source) circa 1950s first major advances in the 1980s
  14. 17.
  15. 18.
  16. 19.
  17. 20.
  18. 21.
  19. 22.

    definition: a computer program or an artificial intelligence which conducts

    a conversation via auditory or textual methods. Such programs are often designed to convincingly simulate how a human would behave as a conversational partner, thereby passing the Turing test. (source) circa 1966 (ELIZA) first major advances in the early 2000s
  20. 23.
  21. 24.
  22. 25.
  23. 26.
  24. 27.
  25. 28.
  26. 29.
  27. 30.
  28. 31.

    Web Speech API: • Speech recognition • Speech synthesis (TTS)

    W3C Community specification was published in 2012 SpeechRecognition interface currently only supported in Chrome, experimental feature Uses Google's servers to convert speech to text (requires Internet connection)
  29. 32.

    "Common Voice is Mozilla's initiative to help teach machines how

    real people speak." (source) Publicly open dataset Upload recordings of your voice Help reduce bias in Natural Language Processing (NLP) & machine learning
  30. 35.
  31. 36.
  32. 38.

    • node.js • serverless (AWS Lambda or Google Cloud Functions)

    • lightweight database (e.g. Amazon DynamoDB) • CI server of choice (e.g. Travis, Jenkins, etc.) • unit testing framework of choice (e.g. Jest) • TypeScript…?
  33. 41.
  34. 43.
  35. 44.
  36. 46.
  37. 48.

    JSON event with intent name and slot(s) Handler function mapped

    to that intent Use SDK to produce a response with speech, audio, etc.
  38. 49.
  39. 50.
  40. 51.
  41. 52.
  42. 53.
  43. 54.
  44. 55.

    • Launch requests • Add intents • Wait for response

    • Handle slots • Add images to cards • Play simple audio • Use SSML • User login (OAuth2) • Persistent data • State management • Contexts (Google) • Dialog management (Alexa) • Advanced audio (Alexa) • Customize display on visual devices • Monetization / transactions • Request user permissions • Notifications • Internationalization
  45. 56.

    • By default, skills in development are only available to

    you • Certification process similar to mobile app store submissions ◦ ~48-hour turnaround on average ◦ Feedback is unpredictable! ◦ Respect existing brands • Can share a "beta" version with co-workers, friends, etc. ◦ Great for QA as well as hobby projects
  46. 58.
  47. 59.

    • The code is not hard • What is hard:

    ◦ Learning about the platform limitations ◦ Managing stakeholder expectations ◦ Understanding & changing user behaviors ◦ QA • It's not just an engineering challenge!
  48. 60.

    • You would think these platforms are ideal for audio…

    but they're not! • It's clear the companies designing these platforms are still focused primarily on Text-to-Speech (TTS) • The Actions on Google audio player is almost unusable • The Alexa audio player has many features but is very unintuitive when you're first working with it
  49. 61.

    • Invisible errors: ◦ The Alexa service / Google /

    Dialogflow can reject a user's request ◦ If that happens, your app is not notified at all! ◦ Logs/analytics can't tell the whole story ◦ Users often don't understand why it failed • Real user testing is critical!
  50. 62.
  51. 63.
  52. 64.