Showing posts from 2018

Google Assistant and Node JS (Miss Duck) V2

Integrate Google Assistant, Dialog Flow V2  with actions-on-google in NodeJS and Nexmo Stitch conversation platform Continues Miss Duck V1 Find the updated Miss Duck project on  GitHub Presentation Video The Google Dialog Flow project is constantly improving, and it really gets interesting to follow. This time while we are integrating Nexmo Stitch (The in app-conversation API from Nexmo) to allow Miss duck send events to a conversation platform. In the presentation above you can see about a use case regarding accessibility to a communication platform.  Updating Miss Duck Update Dialog Flow V2 Navigate to your Dialog Flow agent and enable V2 that is officially released Dialog Flow agent settings NodeJS actions-on-google Update your NodeJS library to ^2.3.0:  " actions-on-google " : " ^2.3.0 " , Using the most recent version of the actions-on-google library will help you stay aligned with the latest Dialog Flow updates.  Y

JS Monthly, July Event

JS Monthly, July Event Tuesday, July 31, 2018 See 🦆 Miss Duck 🦆 in Action 🤩 Excited to give a talk in  JS Monthly meetup (Tuesday, July 31, 2018) about accessibility for online communication platforms!  Presentation slides

Dynamically setting variables with Grunt

Set API Keys based on the deployment environment. The problem During the development of a web project, probably you will be using test API keys and other 'sensitive' information that you will need to remember to replace before every commit / deployment. For tasks like this that can lead to big headache, it seems like a great opportunity to automate . Either as part of CI or even as part of your daily routines. Description The idea is your environment to hold the sensitive information (environment variable). When the grunt task runs, picks up the variable value, and defines a local (in the task) variable. Then another task is searching in your files for the 'placeholder', and replaces the string with the actual variable. The output file that is generated (including the sensitive information), goes to a folder that is public to your server. Furthermore, the destination folder (dist) is included in .gitignore to avoid pushing to the repo. Step by step L

Google assistant says hello to your nodeJS service V1

Google Assistant and NodeJS service. Google assistant Action (application) that you can create and deploy in a few easy steps. (Part 2) Overview: Get a nodeJS service to drive a communication over Google Assistant. Assuming you have a google Deverloper account and know how to go through the basic configuration. The steps bellow are filtering out all the confusing options you have on how to interact with Google Assistant. We will create an Action (Think of it as an application that the Google assistant launches on user's request). Then we will use the DialogFlow to configure the Intents (trigger words) that will forward the data to a nodeJS service that we will setup. Invoke the first call to your script Create/Import a google project Creating the project is pretty straight forward. Make sure to pick a name for your assistant that will be easy to pronounce and the speech recognition will understand. It will make your life easier here, if you pick a commo