And thus your app would have to decide what to do based on the text spoken or typed in by the user. Meaning: You have one intent that has to deal with nearly all possible user input. If you were to build a more complex app with the Actions SDK, you would use one intent most of the time:. And if the Assistant detects that one of those phrases was used by the user, it starts up your app using this intent. You might even add some parameters to that (for example numbers or a date). Or it might kind of introduce the app to the user in some way.įor the start of your app you can also define custom intents and which user utterances trigger that intent. Depending on your kind of app, this intent might directly provide the answer and then stop the app. In contrast to Android, though, you are very limited when it comes to intents with the Actions SDK.Įvery app has to define one intent, that is used to start up your app, if no custom intent is better suited to the invocation phrase. An intent specifies what the user intends your app to do. And with Actions on Google, they are not much different.
I only added one more action to make it a better sample for this post. The sample app would work well as a one-shot app. In this case, the app has only one action and answers directly with the response the user is looking for. But often it makes sense to create a one-shot app. For a truly conversational app, where there's a dialog between the user and the assistant, apps have multiple actions. The relevant things you need to know are:Īn action is a wrapper combining an intent and the fulfillment for this intent. Let's go a bit more into the base concepts here. As the name of the SDK implies, you can create actions which basically are speech snippets of your user and your response to them. The Actions SDK is one way to develop apps for the Google Assistant. Thanks to botsociety.io, you can even see this website showcasing this prototype. After the last response, the app finishes - and with this also the current assistant's action.
The second and third are responses of the app. The first is by the assistant itself - I changed the color for that one to emphasize the difference. Here's a sketch of what a conversation with this app should look like: Sample dialog of the app - Made with botsociety.io Then, in the next post, I'll build an improved version with Dialogflow. The first version in this post with the Actions SDK.
Thus an assistant app that tells me when the next buses are due and whether we should hurry up or whether we can idle around a bit more is what I'm going to build. We do have an app for bus information in Münster - but some limitations of this app make it not really suitable for the task. So I wonder every morning when to leave for the bus. In winter and also due to some long-lasting street works, one of the two lines near our home is quite late all the time. In my hometown, I usually take the bus when taking our youngest to kindergarten before heading off to work. After reading both posts you hopefully will know enough to decide which approach is better suited for you. My next post will use Dialogflow (formerly api.ai) instead.
For developing this app, I will be using the Actions SDK.
#Api . ai actions how to#
In today's post, I'm going to show how to develop a simple app for the Google Assistant.
0 kommentar(er)
