Two Voice Devs

Based on a question from Dana Gibson, Mark and Allen discuss some of the complexities when it comes to building Actions on Google for Assistant or Alexa Skills that access a database. From dealing with the asynchronous operations to making sure we complete the queries as quickly as possible, from SQL to tools like Firebase, Dynamo DB, and Air Table, we explore some tips and traps about databases in a #VoiceFirst world.

An important feature in Account Linking with both Amazon Alexa and the Google Assistant is how they both integrate with existing authorization systems using the OAuth2 protocol. But OAuth2 can be tricky sometimes, as Mark and Allen relate with some tales of woe as they've tried to integrate OAuth into their #VoiceFirst skills and actions. Definitely some weird stuff happening!

With another week to ponder the implications (and implementation), Mark and Allen are both pretty excited to discuss some thoughts around what a #VoiceFirst CMS might look like and how it would work with the Actions for Google Assistant and Amazon Alexa. Specifically, we dig a little bit into what Multivocal and Jovo are currently doing to make things easier on developers and content creators and what more needs to be done.

Allen and Mark continue their conversation about Content Management Systems in a #VoiceFirst world and how developers could use a CMS to both simplify their development, empower the content authors and conversation designers, and lower the cost of updating Google Assistant actions and Alexa skills.

Some products discussed:

When it comes to #VoiceFirst applications, we often say that "content is king". But creating great conversations are also part of the content, and require close collaboration between the content author, the conversation designer, and the developer. Frequently updating the content can make for a better Alexa skill or Google Assistant action, but could be complicated. Mark and Allen discuss how (and why) to make this easier using a voice-oriented Content Management System (CMS).

Some products discussed:

What #VoiceFirst technology would we use to build an Alexa Skill or Google Assistant Action that allows us to chat with our friends? That's the question that Allen and Mark try to answer. Along the way, we learn about various technologies, tips, and tricks that we can use across an assortment of voice apps that we may build. (But should we even try to make this?)

Let's get this #VoiceFirst app going! Mark and Allen chat about some of the complexities when it comes to starting your Google Assistant Action or Alexa Skill - either as the start of a conversation, through a "deep link" invocation, or as a "one shot" question or command. While it seems like it should be straightforward, things aren't as easy as they seem! What tricks and tools do we have at our command?

Frequent listener JT asked us to explain what "modality" means. Good question, JT! Allen and Mark tackle the question to try and explain it, how it is important in #VoiceFirst development, and discuss some thoughts about where this important consideration may shape our Google Assistant actions and Alexa skills in years to come.

Mark and Allen take a look at one of the foundational technologies for Alexa Skills and Google App Actions (and all of the modern web) - HTTP. Although originally standing for the HyperText Transfer Protocol, these days it has grown to support a wide range of uses, including the REST protocol, which many #VoiceFirst apps use to make information available for users.

Mark is joined by guest host Eliza Camber, an Android developer and Google Developer Expert for the Google Assistant, to discuss what App Actions for the Google Assistant on Android are, how they bring the power of #VoiceFirst features to new and existing Android apps, how they compare to Alexa's mobile features, and how mobile devices can help future assistants with the thorny question about context.