De­sign process for voice

Here are a few point­ers when de­sign­ing voice ex­pe­ri­ences for Alexa.

net magazine - - PROJECTS -

Iden­tify the user in­tents When de­vel­op­ing your skill, it’s im­por­tant to iden­tify a list of all the things the user can do within the skill be­fore plan­ning the ut­ter­ances. For ex­am­ple, the user might be able to up­date web­site con­tent, up­date the web­site style and read posts.

Be sure to make use of the built-in in­tents: you can see a full list of them at https://de­vel­oper.ama­­tom-skills/ stan­dard-built-in-in­tents.html. Iden­tify the ut­ter­ances Think about how your user may com­mu­ni­cate with Alexa. To up­date a style, the user might say ‘Up­date back­ground to red’.

It’s also im­por­tant to plan for mis­com­mu­ni­ca­tion. Alexa might in­ter­pret ‘red’ as ‘ref’. A good way to deal with this would be by us­ing the code be­low: ‘ Un­han­dled’: func­tion () { this. emit(‘: tell’, ‘ I am sorry, I didn’t un­der­stand your re­quest. Please try again.’); }, Cre­at­ing a script Make sure you plan out the script be­tween the skill and your user. Be sure to keep in­ter­ac­tions short but enough so that the user un­der­stands how they need to re­spond.

Be­low is a good con­ver­sa­tion flow be­tween Alexa and user. User: ‘Could I up­date my header to blue?’ Alexa: ‘Sure, I can up­date your header to blue. Would you like that

change to hap­pen im­me­di­ately?’ User: ‘ Yes please!’ Alexa: ‘Great, that change has gone live!’

Newspapers in English

Newspapers from Australia

© PressReader. All rights reserved.