If you haven’t done so, install Node.js and then install alexa-app-server, using the instructions outlined in the linked posts.Ĭlone CakeBaker into the alexa-app-server/examples/apps directory by opening a new terminal window and entering the following within the alexa-app-server/examples/apps directory: To complete the experiment, we’ll need a working installation of alexa-app-server and Node.js. We’ll be improving this source code so that it supports saving and loading cakes to the database. Let’s get started by downloading the source code for CakeBaker. If you haven’t yet done so, read our posts on setting up a local environment and implementing an intent-they will guide you in setting up a local development environment for this skill, which will involve more advanced requirements. This experiment will use Node.js and alexa-app-server to develop and test the skill locally, so we will need to set up those dependencies first. We’ll also test the database functionality in our local environment using the alexa-app-server and alexa-app libraries we discussed in our post on implementing an intent in an Alexa Skill. Let’s fix that by implementing two new methods in our skill, called saveCakeIntent and loadCakeIntent, which will allow users to save and load their current progress to and from a database. Right now, that means that a user would be forced to start over at the first step, losing the progress made. But what if the skill closes before the user is able to finish a step? By default, Alexa skills close if a user doesn’t respond within 16 seconds. This continues until the user reaches the last step. A user interacts with CakeBaker by asking Alexa to start a cake, then advances through the steps of the recipe by saying “next” after each response, like so: The skill, a cooking assistant called CakeBaker, guides users in cooking a cake, step by step. Let’s Bake a Cake with CakeBakerįor this experiment, we’ll build upon an existing codebase and improve it.
You can see this at work in skills like the 7-Minute Workout skill, which allows users to keep track of and resume existing workouts, or when users want to resume a previous game in The Wayne Investigation.
RUN LOCAL DYNAMODB SHAREDDB LOCATION HOW TO
We’ll go over how to write Alexa skill data to storage, which is useful in cases where the skill would time out or when the interaction cycle is complete. In this post, we’ll implement persistence in a new skill so that users will be able to access information saved from their previous interactions. Then we tested the skill in the simulator and on an Alexa-enabled device. We tested the model and verified that the skill service behaves as expected. Editor’s note: This is the fourth post in our series on developing Alexa skills.īy now, we’ve made a lot of progress in building our Airport Info skill.
0 kommentar(er)
