<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Pavel Gvay on Medium]]></title>
        <description><![CDATA[Stories by Pavel Gvay on Medium]]></description>
        <link>https://medium.com/@pavelgvay?source=rss-4dd25ffa6a72------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*BgqogoueahoOkU4BdVxIIA.jpeg</url>
            <title>Stories by Pavel Gvay on Medium</title>
            <link>https://medium.com/@pavelgvay?source=rss-4dd25ffa6a72------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 07:29:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pavelgvay/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Voice and conversation UI design best practices (+ PDF cheat sheet)]]></title>
            <link>https://medium.com/tortu-blog/voice-and-conversation-ui-design-best-practices-pdf-cheat-sheet-2f0e59adea3c?source=rss-4dd25ffa6a72------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f0e59adea3c</guid>
            <category><![CDATA[vui-design]]></category>
            <category><![CDATA[alexa]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[chatbot-design]]></category>
            <category><![CDATA[google-assistant]]></category>
            <dc:creator><![CDATA[Pavel Gvay]]></dc:creator>
            <pubDate>Wed, 25 Sep 2019 14:45:10 GMT</pubDate>
            <atom:updated>2020-11-06T09:48:34.991Z</atom:updated>
            <content:encoded><![CDATA[<p>Conversation design is right here for some time already. Starting from chatbots to Google Assistant and Amazon Alexa making its way into more specific domains of our day-to-day life. Still, too often than one might imagine, the conversation fails, despite the fact that it has been designed by humans for humans. Reasons vary but perhaps, the most common is lack of investigation of human communication rules.</p><p>Today I will share the best practices of VUI taken from real apps where designers spent considerable amount of time on testing and learning. This tutorial is super easy and compelling made in the form of Dos and Don’ts with the description of each case. I also compiled a short and clear-cut PDF with examples illustrating each case (see the end of this tutorial).</p><p><strong>TL;DR:</strong> <a href="http://bit.ly/vui-design-cheat-sheet">Download the PDF cheat sheet</a> with all the examples from this article put in short.</p><h3>General</h3><h4>Be brief and clear</h4><p>Since you design the conversation on paper first, do not forget about the fact that your users won’t be able to read (or go back to that needed point) the text. And we, humans, have quite limited short-term memory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v9937QRmwtxX2wejaKtstg.png" /></figure><h4>Diversify your language</h4><p>A welcome phrase (or any other phrase repeated many times) might become a nuisance. So, write several variants of the phrase and teach your app to adapt to the context; this will provide more natural flow and add common sense to the conversation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hAMvEUE9goY_I7l7d7uIPQ.png" /></figure><h3>Greetings</h3><p>Three main steps should be accomplished in your app at the stage of greeting a user:</p><ol><li>Be polite and welcome a user.</li><li>Explain what the app does</li><li>Turn the floor over to the user</li></ol><h4>Be polite</h4><p>Don’t forget to use those magic words which we were taught as kids; they do magic and facilitate communication process by making user more loyal to the errors occurring during conversation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u9MW1yGm3noGSfRp7uULXw.png" /></figure><h4>Tell users what the app does</h4><p>At first users can only guess what exactly the app does; and different users naturally have different mindsets. The best way to avoid first touch frustration is to tell users what the app does. And obviously, the faster you relieve the stress the better. So, do it straight after a welcome phrase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jHUG0Wz0N0ZRulUJAM-ifw.png" /></figure><h4>Turn the floor over to the user</h4><p>Make it clear for a user that now it’s their turn to start acting. And a properly asked question is the best tactics for showing users it’s high time to act.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IYMrWsgALiClJhbmLDLsCw.png" /></figure><h4>Avoid over-promising</h4><p>Basically, a user decides whether to proceed interacting with an app or not during first exchanged phrases. It’s critical to set clear value from the first seconds of interaction. Do not stumble users with overpromising since it may lead to wrong requests (something your app wasn’t ready for) and as a result to errors, miscommunication, and disappointment. Explain what to expect from the start and don’t be afraid to seem too simple. The less an app does the better it works, the clearer users see the value.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JXgDW78Uxrm0Ct3yt705Jg.png" /></figure><h4>Mind the context</h4><p>If you are so lucky to get a user come back to your app for more, adequate reactions of the app based on users’ invocations will be very handy. It’s really dull and annoying to hear the same phrase all over again, especially when a user changes the request.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HoT6ZjszN2Vn2paQWJFY4A.png" /></figure><h3>Prompts</h3><h4>User’s response is needed — make it clear</h4><p>First of all, you need to give users clear understanding that the system is waiting to their move. And presenting the options only doesn’t mean anything.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QAE7uyMUlVzKcVpylT6OBA.png" /></figure><h4>Help forming an anticipated answer</h4><p>The most frequent reason for dialogue error is a question asked in the wrong manner. Obvious, as it seems, the system is trained to understand exact key-phrases; so, when a user picks a “wrong” phrase the whole dialogue fails. Make sure, you put a user on the right track for proceeding a dialogue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GA9kt0uGkHEnUFjzsVf2BQ.png" /></figure><h4>Giving options of answers is a must</h4><p>When the number of options is limited.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UWyCppfOBX1Z2P_-vXWY3g.png" /></figure><h4>One question at a time, please</h4><p>This is correct for human communication and it’s the only possible way for human-machine communication.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H5qAZFl3fW638xMV_58ZMQ.png" /></figure><h4>Questions last</h4><p>In writing we start from the most important statements. Everything is structured when put on paper. You can go back to that point, reconsider it. In spoken language, however, we tend to place the most important info in the end of the speech.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VqahqugmAuIckWzdHkdiyA.png" /></figure><h3>Informational Statements</h3><h4>Prepare users for consuming a piece of information</h4><p>When seeing a person next to us we’re generally tuned into the conversation. Talking to a computer or a smartphone implies different mindset. Users expect more formal way of communication from a machine, which actually makes it easier to understand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ga6HEOTOMt1U4GgqcLgzrQ.png" /></figure><h4>Use SSML</h4><p>No way around it. Machines were taught to talk to imitate human interaction. The only way to make machines more human and the conversation more real is to use SSML for speech mark-up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AoDUYG4VLT_HKRUyvK-q2w.png" /></figure><h3>Outro</h3><p>And this is really just the icing on the cake. The topic of VUI is so large thanks to the pace of tech progress that I can see as far as at least three more articles on this subject. So let me know if you’re interested in the next part by clapping (you can clap several times!).</p><p>I also made <a href="http://bit.ly/vui-design-cheat-sheet">a PDF with all the examples from this article put in short</a>. Learn more — do better!</p><p>However, these are just common insights based on a lot of different apps tests. Each product is unique in terms of users it aims at. So, one of the most integral parts for a successful app launch is testing with real users. This is the only way to make a truly memorable experience via your product. And I assure you, you will be amazed by the answers and reactions real people (not your imaginary users) will show interacting with your product.</p><p><a href="https://fabble.io/">Fabble (formerly Tortu) allows for prototyping and testing your ideas at any stage</a> — which is crucial since it enables you to save time, effort, and money. Welcome to the community of those who care about user experience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f0e59adea3c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tortu-blog/voice-and-conversation-ui-design-best-practices-pdf-cheat-sheet-2f0e59adea3c">Voice and conversation UI design best practices (+ PDF cheat sheet)</a> was originally published in <a href="https://medium.com/tortu-blog">Fabble Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[VUI design practice review — Atom Tickets]]></title>
            <link>https://blog.prototypr.io/vui-design-practice-review-atom-tickets-e8890c06aef8?source=rss-4dd25ffa6a72------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8890c06aef8</guid>
            <category><![CDATA[voices]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[vui]]></category>
            <category><![CDATA[vux]]></category>
            <category><![CDATA[alexa]]></category>
            <dc:creator><![CDATA[Pavel Gvay]]></dc:creator>
            <pubDate>Mon, 17 Dec 2018 10:59:54 GMT</pubDate>
            <atom:updated>2018-12-17T10:59:54.804Z</atom:updated>
            <content:encoded><![CDATA[<h3>VUI design review — Atom Tickets</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/967/1*9FKvYcNj53JpyTl3ChkeBw.jpeg" /><figcaption>Photo: <a href="https://medium.com/u/54075283df8f">Rahul Chakraborty</a>, <a href="https://unsplash.com/photos/nGzvZe1iWOY">Unsplash</a></figcaption></figure><p>There are a lot of materials how we should design voice applications — articles, guidelines, conferences’ reports. But how actually is it going in real life?</p><p>In this article, I’ll review Atom Ticket application for purchasing tickets to the cinema from the design point of view. I’ll try to highlight both the good and bad sides. Have a nice reading.</p><h3>About the author</h3><p>Before I start the review, I want to introduce myself. I have been dealing with the voice application design for two years. For this time I have already participated as a speaker at 4 conferences, learned a lot of materials, and even written some my own. Also, I’m creating my own VUI designing tool. As a VUI-designer, I communicate a lot with other VUI designers and every time I try to learn something new from them.</p><p>This review is not the ultimate truth. I just hope my experience is enough to highlight obvious issues in design and to give some useful advice. In case I miss something or did a mistake, I’ll be glad to discuss it at commentaries.</p><h3>The application review</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tht8G-LwIK4XUF_Q1CgE9A.png" /><figcaption>Atom Tickets website</figcaption></figure><p>For my review, I chose <a href="https://www.amazon.com/Atom-Tickets/dp/B07BMD7M3Z">Atom Tickets</a> Alexa skill. This app lets people buy tickets right from the smart speaker. I chose this one because I wanted to consider the scenario which often occurs with regular users of smart speakers. The ticket buying scenario seemed to me as a suitable variant.</p><p>Conventionally we can divide the app into two basic parts:</p><ol><li>The ticket purchase. It consists of location’s specification, the choices of film, cinema and time.</li><li>The film’s release info. The app lists films, those are released at a cinema or gonna be released soon.</li></ol><h4>Happy path script</h4><blockquote><em>Me:</em> Launch Atom</blockquote><blockquote><em>Atom:</em> Welcome to Atom Tickets, the best way to go to the movies. You can buy tickets or browse movies. What would you like to do?</blockquote><blockquote><em>Me:</em> Buy tickets to “Green Book”</blockquote><blockquote><em>Atom:</em> Let’s find theaters near you. What’s your ZIP code?</blockquote><blockquote><em>Me:</em> 94102</blockquote><blockquote><em>Atom:</em> Do you want to see the movie today?</blockquote><blockquote><em>Me:</em> Yes</blockquote><blockquote><em>Atom:</em> Okay, there are 5 theaters near you. Say the name of the theater you want or to hear more say “next”. AMC Metreon 16, AMC Van Ness 14, AMC Kabuki 8. Which theater?</blockquote><blockquote><em>Me:</em> AMC Metreon 16</blockquote><blockquote><em>Atom:</em> Okay, now let’s pick a showtime. Available showtimes are: 11:55 AM, 3:25 PM, 7:05 PM, 10:25 PM. Which showtime?</blockquote><blockquote><em>Me:</em> 10:25 PM</blockquote><blockquote><em>Atom:</em> Please check the Alexa app and enable permissions for Amazon Pay. To return to this point relaunch the skill by saying “Alexa, ask Atom to buy tickets”. Goodbye!</blockquote><blockquote><em>*End of the conversation*</em></blockquote><p>Yes, I don’t have Amazon Pay, and I didn’t want to buy tickets, so that’s why I gonna do the app review till this part.</p><p>All my journey through the application I put at Tortu. <a href="https://tortu.io/share/b1e282">You can launch the app’s prototype, watch the flowchart or look through the utterances here.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pcK4yufpw26gK8ybXwB8Pw.png" /></figure><h3>Problems</h3><h4>Problems with confirmation</h4><p>As it told at <a href="https://designguidelines.withgoogle.com/conversation/conversational-components/acknowledgements.html">Google Conversation Design Guidelines</a> — “Confirmations give users feedback on how their input was understood.” The application has a lot of such problems, and since it is an ordering movie ticket so a user must be 100% sure the app understands his order right.</p><p>Let’s review the problem with the following examples:</p><blockquote><em>Atom:</em> Let’s find theaters near you. What’s your ZIP code?</blockquote><blockquote><em>Me:</em> 94102</blockquote><blockquote><em>Atom:</em> What movie do you want to see?</blockquote><p>or</p><blockquote><em>Atom:</em> What movie do you want to see?</blockquote><blockquote><em>Me:</em> “Green Book”</blockquote><blockquote><em>Atom:</em> Do you want to see the movie today?</blockquote><p>In this case, the user is not sure, has the application understood him right. The correct example could be like this one:</p><blockquote><em>Atom:</em> Let’s find theaters near you. What’s your ZIP code?</blockquote><blockquote><em>Me:</em> 94102</blockquote><blockquote><em>Atom:</em> Okay, San Francisco, California. What movie do you want to see?</blockquote><p>or</p><blockquote><em>Atom:</em> What movie do you want to see?</blockquote><blockquote><em>Me:</em> “Green Book”</blockquote><blockquote><em>Atom:</em> “Green Book”, nice choice! Do you want to see it today?</blockquote><p>The problem occurs not only in cases where we specify the location or choose the film but also in another case such as when the user choose the date, cinema or showtime. It’s impossible to know the details of your order or ask something like “What film have I named?” therefore the problem becomes more important.</p><h4>Excessive confirmation</h4><p>At some moments the application grants a user the redundant choice or asks him an open question without any context.</p><p>Example:</p><blockquote><em>*I told the app I want to buy tickets. The app specified my location*</em></blockquote><blockquote><em>Me:</em> I’m in San Francisco, California.</blockquote><blockquote><em>Atom:</em> Okay, I’ll use San Francisco as your search location. For the next step say “continue”. What would you like to do?</blockquote><blockquote><em>Me:</em> Continue</blockquote><blockquote><em>Atom:</em> Do you want to see the movie today?</blockquote><p>I have already been in the purchasing tickets scenario and actually, it isn’t clear why the app aborted the flow with the phrase “For the next step say “continue”. It’s not enough that this phrase is like an obvious tip (to buy something, say “buy”), but it leads astray.</p><p>The correct variant:</p><blockquote><em>*I told the app I want to buy tickets. The app specified my location*</em></blockquote><blockquote><em>Me:</em> I’m in San Francisco, California.</blockquote><blockquote><em>Atom:</em> Okay, I’ll use San Francisco as your search location. Do you want to see the movie today?</blockquote><p>Thus, we got rid of the unnecessary step and open question, which could potentially lead us to unintended consequences.</p><h4>Wide-focus questions</h4><p>In general wide-focus questions are actively used at the application. There are cases where such questions are absolutely appropriate, for instance at the welcome-flow, but in another case, we should use more narrow questions.</p><p>The bad example:</p><blockquote><em>Me:</em> browse</blockquote><blockquote><em>Atom:</em> You can browse movies that are playing or coming soon, or I can give you a recommendation. What would you like to do?</blockquote><p>or</p><blockquote><em>Atom:</em> Okay, I can walk you through buying tickets for “Green Book”. To start the process say “buy tickets” or to exit say “stop”. What would you like to do?</blockquote><p>The problem with wide-focus questions occurs when a user is already in the course of completing a random flow. Our aim is to help him complete it, so the open question may leads him astray.</p><p>The correct example:</p><blockquote><em>Me:</em> browse</blockquote><blockquote><em>Atom:</em> Would you like to browse movies that are playing or coming soon? Also, you can ask me for a recommendation.</blockquote><p>or</p><blockquote><em>Atom:</em> Okay, I can walk you through buying tickets for “Green Book”. Would you like to continue?</blockquote><p>Narrowing the question is a hint for a user that only he can tell us the proper way of his activity. He hasn’t to guess what the app wants to hear from him. This is no doubt positively reflects on the conversion of the completing this flow.</p><p>Moreover, the open question may put the user expectations too high and then a user may ask what is not provided by the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rn_xPTpwzbXCO_xShM6JDw.png" /></figure><h3>Strong points</h3><h4>Greeting</h4><p>The greeting is elaborated well at Atom tickets. When we are launching the app for the first time, we are welcomed with the phrase:</p><blockquote><em>Me:</em> Launch Atom Tickets</blockquote><blockquote><em>Atom:</em> Welcome to Atom Tickets, the best way to go to the movies. You can buy tickets or browse movies. What would you like to do?</blockquote><p>There are three things I liked:</p><ol><li>The right structure. The skill welcomes the user, sets expectations, lets the user take control. It is the right sequence and there is nothing unnecessary.</li><li>Setting the expectations without overpromising. The app tells at once the things it lets us do — buy tickets or browse movies, it doesn’t overpromise.</li><li>Avoiding the obvious tips. The phrase “You can buy tickets or browse movies. What would you like to do?” not only sets the promises right but also hints the user at how he can interact with the app without any obvious tip. Atom Tickets doesn’t say “To buy tickets, say “buy tickets”, it prompts the user with the natural way.</li></ol><p>Moreover, when you launching the app for the second time, the app greets you in another way.</p><blockquote><em>Me:</em> Launch Atom Tickets</blockquote><blockquote><em>Atom:</em> Hello again. Thanks for coming back to Atom Tickets. What would you like to do?</blockquote><p>Firstly it saves us from unnecessary hints and saves our time. Secondly, every time we can hear the different greeting so it makes the conversation more natural.</p><h4>Appropriate usage of narrow questions and wide-focus questions.</h4><p>I have already touched on this theme, but now I want to focus on the good examples in the app.</p><p>The good example of the wide-focus questions usage:</p><blockquote><em>Atom:</em> Welcome to Atom Tickets, the best way to go to the movies. You can buy tickets or browse movies. What would you like to do?</blockquote><p>This is a part of greeting, the user is not at any flow yet, therefore the wide-focus question is appropriate. We grant him the freedom of choice.</p><p>The good example of the narrow-focus questions usage:</p><blockquote><em>Atom:</em> AMC Metrion 16, AMC Van Ness 14, AMC Kabuki 8. Which theatre?</blockquote><p>The user raises the order here, and the app specifying some details. The narrow question lets a user give the information to the app very exactly. The app knows the certain information about what kind of information a user interested in.</p><h4>The right phrase construction</h4><p>As it was highlighted at <a href="https://voicebot.ai/voice-ux-best-practices-ebook/">VUX Best Practices book</a> by <a href="https://voicebot.ai/">Voicebot</a>, it’s very important to keep the order of the phrase construction right.</p><p>There is at the world of the GUI a user reads only some first lines and passes other. In the case of VUI, the situation is right on the opposite side. The user may listen to the first part of the phrase but certainly remembers the last words. Therefore it is important to place questions at the end of the message.</p><p>Good examples:</p><blockquote><em>Atom:</em> Okay, there are 5 theaters near you. Say the name of the theater you want or to hear more say “next”. AMC Metreon 16, AMC Van Ness 14, AMC Kabuki 8. Which theater?</blockquote><p>or</p><blockquote><em>Atom:</em> Last time you searched for a Green Book. Continue buying these tickets?</blockquote><h4>Using the acknowledges</h4><p>As <a href="https://designguidelines.withgoogle.com/conversation/conversational-components/acknowledgements.html">Google Guidelines</a> tells: “Acknowledgements assure users that their input was received.” The app hasn’t any issue with this statement. Every time I give the app some information it confirms it has got it.</p><p>Good example:</p><blockquote><em>Atom:</em> Last time you searched for a Green Book. Continue buying these tickets?</blockquote><blockquote><em>Me:</em> No</blockquote><blockquote><em>Atom:</em> Okay. What movie do you want to see?</blockquote><h4>Error handling</h4><p>The application is fluent at handling the situations where something went wrong. It not only repeats the question but also grants us additional information.</p><p>Good example:</p><blockquote><em>Atom:</em> AMC Metrion 16, AMC Van Ness 14, AMC Kabuki 8. Which theater?</blockquote><blockquote><em>Me:</em> *<em>unresolved speech*</em></blockquote><blockquote><em>Atom:</em> No results for *<em>repeats my words*</em>. Please pick form the list. AMC Metrion 16, AMC Van Ness 14, AMC Kabuki 8. Which theater?</blockquote><p>Let’s suppose a user didn’t understand he has to answer the question “Which theatre”. In this case, the application not only repeats the words after the user (it dispel doubts about he simply wasn’t understood right) but also hints him what exactly he has to do — pick the theatre from the list.Informational Statements</p><h4>Information statements</h4><p>Before the app will give some information, it explains what exactly will be told. It helps a user to set himself for those data, which the app gonna tell him.</p><p>Good example:</p><blockquote><em>Atom:</em> Okay, there are 5 theaters near you. Say the name of the theater you want or to hear more say “next”.</blockquote><blockquote><em>Atom:</em> AMC Metrion 16, AMC Van Ness 14, AMC Kabuki 8. Which theatre?</blockquote><p>Hearing the app is gonna read out the list of the theatres the user is mentally prepared to receive the information. If there won’t be such warning, the user probably would listen to some first items at the list as he wasn’t prepared to receive this information.</p><h3>Conclusion</h3><p>Generally, I liked the Atom Tickets App. The interaction with it was clear and simple. The app told me what it can do right away, so I without any problems was able to order tickets to the necessary movie from the first attempt. In the case where an irregular situation has occurred (I didn’t know the ZIP code), the application dealt with it and suggested simply tell him the city.</p><p>Sometimes problems with information confirmation and open questions led me astray, but nevertheless, I got out of them. I think it is a good point for improvement, and of course, it is not a critical error. And also I haven’t founded any critical errors.</p><p>Tools I used:</p><ul><li><a href="https://tortu.io/">Tortu</a>. I visualised the dialog with this tool, simply adding all my journey points. The prototype mode is pleasant bonus, because saved me from launching skill to go thought the scenario over and over again or simple copy the text.</li><li><a href="https://reverb.ai/">Reverb</a>. Since I was recording all my interactions with the app, it could be conveniently to use Alexa via laptop. Reverb is an ideal tool for it.</li></ul><p>Materials I used at my review:</p><ul><li><a href="https://designguidelines.withgoogle.com/conversation/">Google</a>, <a href="https://developer.amazon.com/docs/alexa-design/intro.html">Amazon</a>, and <a href="https://docs.microsoft.com/en-us/cortana/skills/design-principles">Microsoft</a> guidelines.</li><li><a href="https://community.algolia.com/talksearch/demos/voice_summit/">Some materials from Voice Summit.</a></li><li><a href="https://voicebot.ai/voice-ux-best-practices-ebook/">Voicebot book</a></li><li>My own experience</li></ul><p><a href="https://tortu.io/share/b1e282">The project link.</a></p><p>Summarising all I want to add that I want to discuss those moments where I missed something or did a mistake. What kind of mistakes or strong points you’ve found out?</p><p>Thank you for reading till this point. I want to review more applications, but not sure is it interesting for people. If you liked it please applause to this article, so I can understand how many people are interested in it. By the way, you can hold the Clap Button and clap even 37 times in a row ✌️</p><p><em>P.S: I’m a founder of Tortu, the tool that I mentioned above, so if you have any questions, suggestions or feedback I will be glad to discuss it. Here is my personal e-mail: </em><a href="/service/mailto:p@tortu.io"><em>p@tortu.io</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8890c06aef8" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/vui-design-practice-review-atom-tickets-e8890c06aef8">VUI design practice review — Atom Tickets</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Testing the voice application on the real users before the development]]></title>
            <link>https://medium.com/hackernoon/testing-the-voice-application-on-the-real-users-before-the-development-67560bd8a5c8?source=rss-4dd25ffa6a72------2</link>
            <guid isPermaLink="false">https://medium.com/p/67560bd8a5c8</guid>
            <category><![CDATA[vui]]></category>
            <category><![CDATA[alexa-skills]]></category>
            <category><![CDATA[ivr]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[actions-on-google]]></category>
            <dc:creator><![CDATA[Pavel Gvay]]></dc:creator>
            <pubDate>Tue, 04 Dec 2018 13:41:02 GMT</pubDate>
            <atom:updated>2018-12-04T13:41:02.408Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aqfB5Qzumwbcxkh7sBqkNg.jpeg" /><figcaption>Source: Unsplash (<a href="https://medium.com/u/7ef7644c61e0">rawpixel.com</a>)</figcaption></figure><p>The difference between voice and graphics interfaces is that a user has no restrictions of “screens” and “buttons”, he is able to say anything he wants. Therefore it’s a high priority to know how the user actually uses your application.</p><p>This article I’ll share my own experience of user-testing voice application even before the first code-line has been written. Also, I’ll try to blow apart the myth the user-testing is difficult.</p><h3>When is it the right time to begin the test?</h3><p>The brief answer — as soon as possible. The sooner we can find the mistakes, the easier and cheaper it possible to recover.</p><p>Beginning the testing right after you’ve completed the basic part of your design is an ideal moment. This moment you’ve done enough to check your ideas on real users, but also you haven’t spent much time and resources.</p><p>In general, the testing is not the one-use process. It must be held iteratively. Our team try to start testing applications as soon as possible, then put some improvements, add some new pieces and test again, and so on.</p><blockquote><em>If you aren’t experiencing failure, then you are making a far worse mistake. You are being driven by the desire to avoid it.</em></blockquote><h3>Wizard of Oz technique</h3><p>Let’s suppose we have already done the basic part of the design and faced we want to watch how people will use our application.</p><blockquote>“Wizard of Oz (WOz) testing occurs when the thing being tested does not yet actually exist, and a human is “behind the curtain” to give the illusion of a fully working system.” — Cathy Pearl, “Designing Voice User Interfaces”, 2016.</blockquote><p>We will pretend the application is absolutely ready when we actually have only the medium-fidelity prototype. Then the user will speak to it being sure it’s working. Also, we gonna simulate the work of the app.</p><p>Overall the process will look like we are starting the prototype, the user speaking to it, he can hear the answers and also giving his answers and we are choosing what the prototype should say.</p><h3>The prototype</h3><p>For carrying out the testing we need the medium-fidelity prototype. This is what he must to be able to do:</p><ul><li>Be voiced, so users can hear it</li><li>Give us opportunities to choose the variants of the answer</li></ul><p>Let’s check out the tools which can help us to create such a prototype.</p><p><em>In this article, such tools as Storyline or Sayspring won’t be considered, because this tools can completely make an application and therefore you have no ways to control the user and application dialog.</em></p><h4>TTS tools</h4><p>The first and easiest way is to use any TTS system. If you are developing an IVR, you can play audio files yourself. In other words, on each user answer, we are voicing the text or playing the audio file.</p><p>We can use anything as a tool for voicing the text. It may be Google Translate (where you can voice the text), Google Text-to-Speech or something else.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*arw2aFhy-6XJDXqNNnNcMg.png" /><figcaption>Google Cloud Text-To-Speech</figcaption></figure><p>Google suits me most because it has a wide choice of voices. Also, you can tune the speed and pitch and the tool has TTS supporting.</p><p>Pros:</p><ul><li><strong>Simplicity</strong>. It’s easy to use the tool, there are no any difficulties using it.</li><li><strong>Flexibility</strong>. You can add new prompts right on the go at any unaccounted situations.</li><li><strong>Pricing</strong>. Most tools either completely free or allow to voice a certain amount of symbols.</li></ul><p>Cons:</p><ul><li><strong>Bulkiness</strong>. Every answer has its own opened tab, it is easy to mess up between them.</li><li><strong>Huge time expenses</strong>. A prototype is a kit of tabs, actually, it doesn’t exist. Every time you want to carry out the user testing, you have to open every tab over again and put in the text. Complex application takes more time.</li><li><strong>Detachment from the rest of project deliverables</strong>. For sure you have the sample script, prompt list, flowchart. Highly likely the prototype isn’t connected to them in any way. For example, if you change some phrases in a prompt list you are going to have to manually sync it at every tab. So it will make your work a bit more complicated.</li></ul><p>As a result, this is a pretty simple and of course the working method to carry out the user testing, but he is pretty uncomfortable and time-consuming.</p><p><em>I’ve found two tools which help to improve this process, “gathering” all tabs together. They are </em><a href="https://github.com/bensauer/saywizard"><em>Say Wizard</em></a><em> and </em><a href="https://anilkk.github.io/voicex/"><em>VoiceX</em></a><em>.</em></p><h4>Tortu</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J32FdQ-BkgmsQd0Ox19cvw.png" /><figcaption>tortu.io: Workspace</figcaption></figure><p><a href="https://tortu.io/">Tortu</a> is a tool not just for prototyping. It is more like a VUI designing tool. It lets you map out your conversation into a flowchart, also it helps to keep all your prompts right at flowchart elements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/976/1*Yw9rMcVL9jeReVEUL4PQkQ.gif" /><figcaption>tortu.io: Prototype</figcaption></figure><p>Working methods with <a href="https://tortu.io/">Tortu</a> are simple:</p><ol><li>We create a flowchart of the conversation. If it becomes too big here is an opportunity to divide the flowchart into logically connected parts.</li><li>We write the necessary prompts. For every step of the dialog, we can add an unrestricted amount of prompts variants.</li><li>Launching the prototype and testing the application either with user or ourselves.</li></ol><p>When we are testing the app with a user, actually we are choosing the answer variants at our prototype. So the prototype just reading aloud the replicas on behalf of the application.</p><p>Here is an opportunity to add new branches right on the go. It is very comfortable in such cases when we have some unaccounted situations.</p><p>Also here is a wide choice of voices and also an opportunity to tune the speed and pitch of the speech.</p><p>Pros:</p><ul><li><strong>Simplicity</strong>. You are literally building the conversation with dialog steps on behalf of a user and an application. Then you are simply following the conversation step by step.</li><li><strong>Speed and flexibility</strong>. A prototype creates in one click. A flowchart and prompts are placed at one place, we don’t spend time too sync them.</li><li><strong>Pricing</strong>. The tool is absolutely free.</li></ul><p>Cons:</p><ul><li><strong>No slots supporting</strong>. In cases when a user setting some data, we can’t account them.</li><li><strong>No opportunity to attach your own audio files</strong>. It is highly important to have an opportunity to attach your own audio files to steps when we are testing IVR.</li></ul><h3>Testing tips</h3><p>So you have a clear view on how to test your conversations, we’ve found the user and created the prototype. Before the beginning here are some tips:</p><ul><li>Record your testing sessions. You must record not only the sound but also a video. Nonverbal signals can tell much about a user when he is giving them while speaking to the app.</li><li>Invite one more colleague. You are going to be very busy about controlling the prototype and speaking with a user. And additional mind helps you to notice things you won’t.</li><li>Analyze results with a whole team or share them with it. It’s very important when the whole team is aware of all improvements. Remember there are always some improvements after the test.</li><li>Learn more sources about user testing. More knowledge helps you to receive more information from one session. I recommend beginning with a Chapter 6 of <a href="https://www.amazon.com/Designing-Voice-User-Interfaces-Conversational-ebook/dp/B01NALL1Q0">Cathy Pearl “Designing Voice User Interfaces” book</a>.</li></ul><h3>Conclusion</h3><p>Testing with users always goes beyond the borders of your comfort zone. Therefore sometimes it’s difficult not to shy away from it. This article I tried to show it is not so difficult as much people think.</p><p>It’s obvious I haven’t reviewed all tools and methods. If you have something to share, I’ll be glad to discuss it with you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67560bd8a5c8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/testing-the-voice-application-on-the-real-users-before-the-development-67560bd8a5c8">Testing the voice application on the real users before the development</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wizard of Oz testing voice apps with Tortu]]></title>
            <link>https://medium.com/tortu-blog/wizard-of-oz-testing-voice-apps-with-tortu-e2148129050d?source=rss-4dd25ffa6a72------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2148129050d</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[vui]]></category>
            <category><![CDATA[ivr]]></category>
            <category><![CDATA[alexa]]></category>
            <category><![CDATA[google-ho]]></category>
            <dc:creator><![CDATA[Pavel Gvay]]></dc:creator>
            <pubDate>Thu, 11 Oct 2018 14:44:54 GMT</pubDate>
            <atom:updated>2018-10-17T11:09:43.337Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*249N2UOzIxbWCzOxZMKyPw.png" /></figure><p>While designing a voice application you should understand how real people will use it. The sooner you make a user testing, the better you will be granted to find the weak points of your application and it gonna be easier to correct them.</p><blockquote><em>If you aren’t experiencing failure, then you are making a far worse mistake. You are being driven by the desire to avoid it.</em></blockquote><p>I will tell how <a href="https://tortu.io/">Tortu</a> helps to do WoZ testing with medium-fidelity prototype before you have written the first code line.</p><h3>Wizard of Oz</h3><blockquote>Wizard of Oz (WOz) testing occurs when the thing being tested does not yet actually exist, and a human is “behind the curtain” to give the illusion of a fully working system.</blockquote><blockquote>Cathy Pearl, Designing Voice User Interfaces (2016)</blockquote><p>We will pretend the application is absolutely ready when we actually have only the medium-fidelity prototype. Then user will speak to it being sure it’s working. Also we gonna simulate the work of the app.</p><p>Overall the process will looks like we are starting the prototype, the user speaking to it, he can hear the answers and also giving his answers and we are choosing what the prototype should say.</p><h3>Before the test</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ple6byWRoQ4LebYl2BsBoA.gif" /><figcaption>Medium-fidelity prototype in <a href="https://tortu.io/">Tortu</a></figcaption></figure><p>Let’s suppose we have already designed the basic flows. Then we decided to invite some users to try our application. We already have the examples of the dialogs, we drew a flowchart and started the work on prompt lists.</p><p>Considering that everything except the dialog examples are inside of <a href="https://tortu.io/">Tortu</a>, we can only recheck everything and start the prototype.</p><p><strong>The prototype possibilities:</strong></p><ul><li>Steps voicing. It’s more than 10 languages, 20+ voices, speed and pitch tuning.</li><li>Adding new steps right at executing prototype in case you’ve found unaccounted scenarios.</li><li>If you have variety of phrases you can choose any of them.</li><li>Undo/Redo. Do you want to come back to another dialog branch? You can rewind the conversation back.</li><li>Support of SSML.</li></ul><p><strong>We are planning to add:</strong></p><ul><li>[DONE] Support of audio files.</li><li>Support of slots.</li></ul><p>Before the start we must have a look at how the prototype works to prevent the unexpected occasions at testing time.</p><h4>During the test</h4><p>So, we have completed the preparation and the user is sitting in front of us. We’ve already spoken to him and told what is gonna be next. So let’s start.</p><p><strong>Step 1. </strong>Set the user the way he won’t be able to watch your screen, but have a possibility to hear the sound of your computer. So this way he may be thinking the system works itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/520/1*X6ymv5TX0aMCu-4WjI7Fzw.png" /><figcaption>TTS settings in Tortu</figcaption></figure><p><strong>Step 2. </strong>Start the application’s prototype. Choose the language, set the voice and tune the pitch and voice speed if needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/519/1*397YnZPIuOVdzXmT-Iv3gA.png" /><figcaption>Dialog branches in the prototype</figcaption></figure><p><strong>Step 3.</strong> Play wizard. Listen to the user and choose the necessary variants at the prototype. The application’s text will be voiced.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/495/1*bLTQECUATxyAApGT5HcM-Q.png" /><figcaption>Adding new dialog steps right in the prototyping process</figcaption></figure><p>In the prototype process there may occur the incidents you didn’t accounted some details at your application. And it’s clear if you want to repair them right now. <a href="https://tortu.io/">Tortu</a> have a possibility of adding new dialog steps right in the prototyping process.</p><h4>After the test</h4><p>Test every scenario this way you planed to do, don’t forget to analyse the results.</p><p>It’s well if you have an opportunity of video recording your test session. So you can not only analyse the user-system dialogs but also users behaviour.</p><p>I’m sure the user testing is an important part of the VUI-applications designing, however much people avoiding it cause of its difficulty. In <a href="https://tortu.io/">Tortu</a> we tried to simplify as much as possible the process of WoZ testing.</p><p>We always looking for the ideas how to improve <a href="https://tortu.io/">Tortu</a>, that is why every feedback is much appreciated. I’ll be glad to speak to you in person at <a href="/service/mailto:p@tortu.io">p@tortu.io</a>.</p><p><em>P.S. I recommend you to read </em><a href="https://www.amazon.com/Designing-Voice-User-Interfaces-Conversational-ebook/dp/B01NALL1Q0"><em>“Designing Voice User Interfaces” by Cathy Pearl</em></a><em>. There is at Chapter 6 a specified analyse of user-testing process of voice applications and not only with WoZ methods.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2148129050d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tortu-blog/wizard-of-oz-testing-voice-apps-with-tortu-e2148129050d">Wizard of Oz testing voice apps with Tortu</a> was originally published in <a href="https://medium.com/tortu-blog">Fabble Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What tool to choose for voice user interface design?]]></title>
            <link>https://medium.com/hackernoon/what-tool-to-chose-for-voice-user-interface-design-b4122f657e44?source=rss-4dd25ffa6a72------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4122f657e44</guid>
            <category><![CDATA[voice-interfaces]]></category>
            <category><![CDATA[voice-ux-tools]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[voice-ux-design]]></category>
            <category><![CDATA[voice-interface-design]]></category>
            <dc:creator><![CDATA[Pavel Gvay]]></dc:creator>
            <pubDate>Tue, 31 Jul 2018 11:42:56 GMT</pubDate>
            <atom:updated>2020-11-06T09:58:05.476Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SCRRa0WchZF7HF3WSB83cQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/251/1*0zlB0QndFhGl1c4-ye1OAg.png" /></figure><p><em>Hi, my name is Pavel. I work at mobile app development company and more than a year ago I actively immersed into the designing process of voice apps.</em></p><p>I took part in several real projects, was the expert of different conferences, met developers of Google Assistant, shared my experience with other VUI designers and after that took a deep thought of how to optimise the designing and testing processes of voice apps.</p><p>This thought gave me a motivational kick to a long journey through existing tools and to an analysis of their limitation, and, well, led me to the expected conclusion — I leave it until the end of the article. Firstly, about present.</p><h3>Theoretical part</h3><p>Let me tell some words about designing voice apps process for those who have never used such interfaces at all.</p><p>Good voice app is different from chatbots that there is no compulsion to use specific commands. The user has an opportunity to build light talk with the service similar with the real life conversation. The main tools are voice and text, but if the device has a screen, the app can add visual accompaniment in the form of cards, carousels, lists with the purpose of the best information delivery.</p><blockquote>For example, let’s have a look at “Pizza order”. Just pretend how many variants of phrases you have to tell the application you want pizza. The user can order some certain pizza, but also he can ask for something with mushrooms and ham. User can ask the application to list all available products and choose the suitable one. Eventually he can just say he is hungry.</blockquote><p>All these arescenarios for the development of the plot and we should provide for each individual step in each possible way in each scenario of the app. What a mess! And we haven’t order a pizza yet!</p><h3>Design Methodology</h3><p>Regardless of a platform VUI design run through the standart set of steps. You can find detailed guidelines on developers page of <a href="https://developers.google.com/actions/design/">Google Assistant</a>, <a href="https://developer.amazon.com/designing-for-voice/">Amazon Alexa</a> and <a href="https://docs.microsoft.com/en-us/cortana/skills/design-principles">Microsoft Cortana</a>. Each team builds its processes in a different way. As for me, I highlight the following steps (sometimes, they run not consistently):</p><ol><li><strong>Identify people from the audience.</strong> Each persona is a collective image of a representative of a group of app audience. Personas help us to understand better user needs and each of them has a certain set of phrases, based on behavioral patterns.</li><li><strong>Filter scripts.</strong> Now we need to decide on what scripts will be implemented in the application. You can not just take and “convert” the graphics app into a voice one. For myself, I derived a simple rule: if it’s impossible to imagine how I pronounce a concrete script with a real person, then we shouldn’t take it to work, because users will definitely have problems with it.</li><li><strong>Create a character.</strong> We should strive to make conversation with the app as similar as a regular talk with a living person. For this the user should form the image of the person with whom he communicates. You can do this by inventing a character. We add a name, draw the exterior, skills, brief biography, character and, of course, voice.</li><li><strong>Write examples of dialogues.</strong> We know who our users are, we know what functionality they want, we know from whose face we speak to users. It’s time to write examples of dialogs between the user and the application for each script.</li><li><strong>Building a dialog tree.</strong> To take into account all the variants of the course of events, all the steps that will lead the user to a hypothetical “pizza order”, it is worth to visualize all the actions. I avoid confusion by drawing a dialog tree in the form of a flowchart.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*jxrvo-8m3S2Ao4mBK8_U8w.png" /></figure><p>6. <strong>Work with phrases.</strong> We want to make the conversation live, so for each replica on the interface side we should have 3+ options. And we want to help developers in speech recognition, so we write several variants of replicas of users.</p><p>7. <strong>Testing. </strong>Are all the branches of the dialogue taken into account, are there no logical dead ends, chopped phrases? For this we need to check our work. I use WoZ testing.</p><h3>Houston, we have a problem</h3><p>The root of all problems of VUI-designers is a huge mass of information. Scenarious, variants of their passage, trees of dialogues, hundreds of steps even in a small application.</p><p>All this info has to be stored somewhere, somehow synthesized, checked, tested, passed on to development, shared with the customer, and there are simply no recommendations in the guidelines from the developers of voice assistants of how to choose appropriate tool.</p><p>After painful and laborious designing my first apps I brought out a specific set of problems:</p><ul><li><strong>Huge map of the dialogue.</strong> Detailed and intuitive way from point A to point B, the entire labyrinth of confusing user’s movement toward the goal. For such a task the regular white board is not suitable. Just imagine how to write all words and then drag them to the developers. And we still have to agree with the team what common symbols we use on the map. Gosh!</li><li><strong>Routine work.</strong> A lot of time has to be spent not only on posting info, but also on synchronizing edits and changes. You can’t place all variants of phrases on the map, so you have to keep them in the Google sheets or whatever. A huge part of the time is spent on manually synchronizing all available information. Since all actions are performed manually and we are not immune from usual human mistakes and typos, we have to recheck ourselves a hundred times.</li><li><strong>Ponderous testing.</strong> Each time to check the quality of the completed work, you have to collect a transcript of the dialogue manually, constantly switching between a document with the transcript, a dialogue map and a table with phrases. This is a terribly tedious and long process, which completely discourages the desire to control the quality of their work.</li></ul><p>The result of this constant struggle with pains is not only the extended development terms, but also the loss of quality due to inattention, tiredless and, of course, loss of motivation.</p><p>Thera are some tools which can facilitate this complicated process. Let’s review them.</p><h3>Evaluation criteria</h3><p>To be objective in my analysis I took one and the same part of the real application that I worked on and tried to implement it with the help of the proposed tools.</p><p>I put all the results into the table and evaluated each set of services according to three basic criteria, estimate them on a 5-point scale:</p><ul><li>Visibility of dialogue map;</li><li>simplicity and quality of testing;</li><li>simplicity of making edits and synchronization.</li></ul><h4>Before you read</h4><p>I and my team are makers of one of the tools below. The main goal of this article is not to promote our tool. The main goal is to fairly tell about the pros and cons of every tool so you could make a decision which tool to use by yourself.</p><p>In my opinion, every team has their own needs so there are no clear winner or loser. I’ll be happy to discuss in comments if I missed something or made a wrong statement. Happy reading!</p><h3><a href="https://realtimeboard.com/">Whiteboard (Realtimeboard)</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2LAG0zvsOAwzV4yKnTplaA.png" /><figcaption>Realtimeboard</figcaption></figure><p>Let’s start from the “classic”: building map of dialogues on a white board, more precisely in its digital equivalent — Realtimeboard. Description of a character and examples of dialogues will be stored in <a href="https://docs.google.com/">Google Docs</a> and phrases in <a href="https://docs.google.com/">Google Sheets</a>.</p><p>I suppose that the mechanism of work is very similar to other similar tools — draw.io, liquidchart and so on.</p><h4>Dialog Map</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/877/1*UI4EUiAhhMEolBt61kyNCQ.png" /></figure><p>Before building a map, you will have to choose your own definitions — it takes a lot of time, but then you get personal framework for your team. When constructing a map, each step is drawn and aligned manually — it is slow, but the map visually becomes clearer.</p><h4>Testing</h4><p>Collection materials process takes a lot of time. It looks like this: take a glimpse into the map, then take the phrase from the table and insert it into the document. No flexibility, solid routine and constant switching between tools.</p><h4>Editing and synchronization</h4><p>It’s easy to edit the map: you can swap the steps, move entire branches and select individual elements in groups. But you have to synchronize the map with the phrases table manually — again the scraping sense of lost data.</p><h4>Summary</h4><p>Realtimeboard gets “four” for the visibility and flexible methodology of designing process. But the testing time is too long and manual synchronization doesn’t make us happy.</p><ul><li>Dialog Map — <strong>5/5</strong></li><li>Editing and synchronization— <strong>0/5</strong></li><li>Testing — <strong>0/5</strong></li></ul><p>Link: <a href="https://realtimeboard.com/">https://realtimeboard.com</a></p><h3><a href="https://tortu.io/">Tortu</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J32FdQ-BkgmsQd0Ox19cvw.png" /></figure><p>Tortu helps you with mapping out your dialogs into diagrams, allows you to store all phrase variants and can build an interactive prototype. For dialogs scripts and persona descriptions we will use Google Docs.</p><h4>Dialog Map</h4><p>The map is constructed from two main blocks — the user step and the interface step. Steps are added and linked conveniently, and also automatically aligned. This saves time. The tool is very flexible and allows you to associate any step with any other, the number of links is not limited. The map can be divided into scenarios.</p><p>However, auto-alligment periodically plays a cruel joke. With large size of a map auto-alignment does not always work correctly and it is difficult “read” the map.</p><h4>Editing and synchronizing</h4><p>Each step on the map, whether it’s a user step or an interface reaction can contain an unlimited number of phrases. This allows us not to store them separately, so there is no problem with manual synchronization. The information is edited conveniently, internal notes can be attached to the steps.</p><p>Working with the map and making edits is also convenient, you can change the steps, rename them, change the links, but there is no drag-and-drop, and also the group selection / copying functions.</p><h4>Testing</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QnILLaHBWhfxtPhx1KAHTw.png" /></figure><p>One click builds an interactive prototype in which we select the steps of the user and the interface alternately. You can see the history and undo the actions. The text is visible on the screen, which means we can read the phrases for typos and watch the history. You don’t waste time for collecting materials and whole process is rather simplier.</p><p>But there is no functionality to test the scripts by voice and even no voice-over for your phrases.</p><h4>Summary</h4><p>The map is visible and easy and convinient in creating and working with. All phrases are inside steps and the re is no porblems with editing and synchronizing. Interactive prototype is built by one click and gives a lot of opportunitis for testing.</p><p>No drag-and-drop function and the difficulty in reading the map depends on the size of it. No voice-over.</p><ul><li>Dialog map — <strong>3/5</strong></li><li>Editing and synchronizing — <strong>4/5</strong></li><li>Testing — <strong>4/5</strong></li></ul><p>Link: <a href="https://tortu.io/">https://tortu.io</a></p><h3><a href="https://www.sayspring.com/">Sayspring</a></h3><p>Maps and phrases are inside Saysprng, info about the character, personas and examples of dialogues are in Google Docs.</p><h4>Dialog map</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G9s3nlXJG-wW8iptTyTbYw.png" /></figure><p>The map is formed step by step: there are notations for user and interface, it can be divided into scripts. At the same time, the map is absolutely linear: transitions are not displayed. It can be done quite quickly and conveniently, but it doesn’t look understandable.</p><h4>Testing</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YNkjloj9SWzUO0tJiU56vA.png" /></figure><p>The service allows you to test the scripts by voice, but the text analogue is not available, there is no possibility to return back into a couple of steps (you have to start from the beginning), speech recognition is available only for three languages and works poorly (or it’s my accent’s fault, sorry). As a voice prototype — okay, but for testing this mode is useless, because there is no possibility to look at the history of the dialogue, get into the phrases, go back a couple of steps. Still have to collect dialogs in a text file to test them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BwKmTTuVPkpsSmFSjFlUjA.png" /></figure><p>Fortunately, the collection of dialogues here is facilitated. By clicking on the button the tool itself will show you the possible dialogs. There are many problems and inconveniences (for example, you can not collect two scripts in one file, you can not download the file, only view it in the tool), but we seriously save time on collecting materials.</p><h4>Editing and synchronizing</h4><p>All replicas are assigned to a specific logical step in the map, which saves us from a table with phrases and the need to switch between tools and synchronize their state. This is a huge plus.</p><p>It is not convient to edit the map by dragging elements only inside one script and without function of grouping steps.</p><h4>Summary</h4><p>Sayspring eliminates the routine work of collecting materials for testing and synchronizing the phrase table with the map, due to the fact that the replicas are fixed after the steps. In a couple of clicks we get an interactive voice prototype.</p><p>The map is unclear, difficult and inconvenient in design process. There is an interactive prototype, but it works only by voice, which makes it useless for testing, as there is no way to get into the replicas, see the history and the unloading of dialogs is limited.</p><ul><li>Dialog Map — <strong>0/5</strong></li><li>Editing and synchronizing — <strong>3/5</strong></li><li>Testing — <strong>3/5</strong></li></ul><p>Link: <a href="https://www.sayspring.com/">https://sayspring.com</a></p><h3><a href="https://botsociety.io/">Botsociety</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BGQhlkEB29ilrbLgwgN75A.png" /></figure><p>The tool is fundamentally different in approach. We write a dialogue, and the map is built automatically. Phrases and characters will be stored in Google Docs.</p><h4>Dialog Map</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qyrT4lKdLNcjWeGz4c5Z1A.png" /></figure><p>On the map, the forks and the connections between the steps are clearly visible. It is interactive: by clicking on the step, the item is opened.</p><p>There is no division into the script, it leads to a large number of repetitions and a huge confusing flowchart.</p><h4>Testing</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/848/1*5jJMrIoTeEPlLnjnLidubA.png" /></figure><p>Testing is carried out in the form of chat, which allows you to get into the replicas, and see the history.</p><p>However, there is no opportunity to control the process, in fact, we just watch the video, not test.</p><h4>Editing and synchronizing</h4><p>For a step, you can specify only one variant of a phrase, so phrases and a map are stored separately. The problem with synchronization remains. It is quite convenient to make edits to the map, there is drag-and-drop function, but you can not select several elements and make a general action over them.</p><h4>Other</h4><p>There is “build-mode” in the service: you can add variables in to phrases and get access to them through API. Thus, the tool can become a content keeper.</p><p>And there is Dialogflow integration which is cool.</p><h4>Summary</h4><p>The tool is created rather for rapid prototyping of simple apps and chatbots. For a full-fledged design, in my opinion, it does not fit. Testing does not work, leaving the problem with the collection of materials open. Downloading dialogs is only available in MP4, GIF or AVI format.</p><ul><li>Dialog map— <strong>2/5</strong></li><li>Editing ans synchronizing —<strong> 2/5</strong></li><li>Testing — <strong>1/5</strong></li></ul><p>Link: <a href="https://botsociety.io/">https://botsociety.io</a></p><h3>Conclusions</h3><p>The results of the research are quite predictable. Every team has its own processes and definitely there is no the best tool. Every tool has its pros and cons. But I hope that this article will help you to pick the perfect tool for you and your team.</p><p>It’s clear, I haven’t researched every VUI design tool, I could miss some of them. I will be glad to discuss at comments both the choice of the certain tool and the design process.</p><p>Thank you for attention 😉</p><p><em>PS. I want to thank Maria Kruglova and Nikita Korneev from mobile-development studio KODE for helping to translate the article into English.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4122f657e44" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/what-tool-to-chose-for-voice-user-interface-design-b4122f657e44">What tool to choose for voice user interface design?</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Welcome to Tortu]]></title>
            <link>https://medium.com/tortu-blog/welcome-to-tortu-256ed82065bf?source=rss-4dd25ffa6a72------2</link>
            <guid isPermaLink="false">https://medium.com/p/256ed82065bf</guid>
            <category><![CDATA[amazon-alexa]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[google-assistant]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[amazon-echo]]></category>
            <dc:creator><![CDATA[Pavel Gvay]]></dc:creator>
            <pubDate>Tue, 24 Jul 2018 14:38:00 GMT</pubDate>
            <atom:updated>2019-04-29T13:26:40.324Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J32FdQ-BkgmsQd0Ox19cvw.png" /></figure><p>A year ago, when I watched Google I/O 2017, I was simply amazed at the capabilities of voice assistants. At that moment I was an android developer and the world of voice interfaces was something completely new for me. I immediately remembered all these fantasy movies that I had seen in my childhood. I could not believe that such a distant and fairy future has already come.</p><blockquote><a href="https://voicebot.ai/2018/03/07/new-voicebot-report-says-nearly-20-u-s-adults-smart-speakers/">Every 5th US adult has a smart speaker at his home.</a></blockquote><blockquote><a href="https://voicebot.ai/2018/03/22/amazon-alexa-skill-count-surpasses-30000-u-s/">Already today, about 40,000 applications have been created for virtual assistants.</a></blockquote><blockquote><a href="https://voicebot.ai/2018/07/10/smart-speakers-to-reach-100-million-installed-base-worldwide-in-2018-google-to-catch-amazon-by-2022/">Smart speakers to reach 100M installed base in 2018.</a></blockquote><p>The very next day I began to develop my first application, digging more and more into this sphere. And until today I don’t stop learning new things, except that I moved from development to design.</p><h3>What’s the matter?</h3><p>Remember how simple applications were in 2009, when AppStore has just appeared, and look at them now. It seems to me that the same thing will happen with voice applications. They will become more and more useful, more functional.</p><p>This means that the complexity of creating voice applications will only grow.</p><p>Today we have devices with which we can talk. These devices are already able to understand human speech. We already have the tools and capabilities to create applications for these devices, so what’s the matter?</p><h3>Problem</h3><p>The more convenient the application, the more comfortable it is to use. The more comfortable the application, the more people use it. The growth of such applications helped the sphere to progress faster.</p><p>The application is not just a code and a device. First of all the application is the interaction between the user and the device, this is a conversation. The most comfortable conversation is a conversation between two people as we do it every day.</p><p>Although today we can not make conversations with the application as flexible as with people, but the more attention we give to VUI (voice user interface) design , the closer we are to it. And this process of designing is not so simple.</p><p>Imagine pizza order application and all these different scenarios of ordering pizza in it: order a pizza by its name, ask the app to advise a pizza, ask the app to tell about it more, ask for additional ingredients and so on. Each scenario should be carefully reviewed and you should take into account all edge cases. Add to this the fact that each person is unique and speaks in his own way, which means that there are hundreds of variants of the same phrases, and we will receive a huge amount of information.</p><p>Tortu will help VUI designers to deal with these information: to collect it, save and share with the team.</p><h3>About product</h3><p>First of all, Tortu is useful in dialogues visualization. In Tortu, each dialogue is represented as a flowchart consisting of dialog’s steps (they can be on behalf of the user or application).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*S1sD6x6aOQX6cJdltII1yQ.png" /><figcaption>“Dialog Map”</figcaption></figure><p>We called this flowchart a “dialog map”. it can be divided into scenarios.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/478/1*VG10H6Rvz5R0BFWcCHrw1Q.png" /></figure><p>Each step in the dialog map is a logical unit that has a name. For example, for the phrase “I want “Margarita”” the appropriate name could be “orders a pizza by name”.</p><p>Moreover, each step is also a repository for variants of phrases — “I want a “Margarita””, “Please, give me a “Margarita””, “I want to try “Margarita” …</p><p>And also you can keep private notes for each step. For example, “Slots: pizza name, pizza size”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/1*VWN-_IaSJ63rkQ76U9wMug.png" /></figure><p>We composed the dialog map, wrote all phrases and saved everything. It is the right time to test your work, isn’t it? By pressing one button the map turns into an interactive prototype, where you can go through the whole conversation step by step. It’s convenient to do both yourself and conduct WoZ testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*7zZJYhSFyLKSnUyu9jDD_Q.png" /></figure><p><a href="https://tortu.io/">All these is already available and you can try the tool here: tortu.io</a></p><h3>Plans</h3><p>Our main goal is to help people to create really convenient and high-quality applications. We believe that VUI design plays an important role and we want to make this process as comfortable as possible.</p><p>Probably our solution is not what it should be and we are very wrong, but sometimes we just need to try. We believe that this problem is worth it.</p><p><a href="http://tortu.io/"><strong>Try Tortu for free.</strong></a></p><p>If you want to share your feedback, tell about a problem, ask questions or tell us any suggestions, we will be very happy to talk with you 🙏</p><p>You can contact us everywhere — here in the comments, at the Product Hunt, <a href="https://tortu.io/about">at the feedback form on our website</a>, by mail <a href="/service/mailto:hey@tortu.io">hey@tortu.io</a>, or to write directly to me -the founder — <a href="/service/mailto:p@tortu.io">p@tortu.io</a></p><p><em>P.S: I express my gratitude to the whole team — Alexey Kozak, Nikolay Nikolenko, Anastasia Voronkova, Ekaterina Tkachenko, Elena Murashova, Dmitry Marchikhin, Valery Shabarin, Anastasia Semina, Boris Rosumnyuk, Maria Kruglova. I am very happy that we do this project together.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=256ed82065bf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tortu-blog/welcome-to-tortu-256ed82065bf">Welcome to Tortu</a> was originally published in <a href="https://medium.com/tortu-blog">Fabble Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>