{"id":4384,"date":"2020-06-24T11:59:46","date_gmt":"2020-06-24T15:59:46","guid":{"rendered":"https:\/\/blog.mozilla.org\/ux\/?p=4384"},"modified":"2020-06-29T15:51:35","modified_gmt":"2020-06-29T19:51:35","slug":"designing-for-voice","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/ux\/2020\/06\/designing-for-voice\/","title":{"rendered":"Designing for voice"},"content":{"rendered":"

In the future people will use their voice to access the internet as often as they use a screen. We\u2019re already in the early stages of this trend: As of 2016 Google reported 20% of searches on mobile devices used voice<\/a>, last year smart speakers sales topped 146 million units \u2014 a 70% jump from 2018<\/a>, and I\u2019m willing to bet your mom or dad have adopted voice to make a phone call or dictate a text message.<\/p>\n

I’ve been exploring voice interactions as the design lead for Mozilla\u2019s Emerging Technologies team for the past two years. In that time we\u2019ve developed Pocket Listen<\/a> (a Text-to-Speech platform, capable of converting any published web article into audio) and Firefox Voice<\/a> (an experiment accessing the internet with voice in the browser). This blog post is an introduction to designing for voice, based on the lessons our team learned researching and developing these projects. Luckily, if you’re a designer transitioning to working with voice, and you already have a solid design process in place, you\u2019ll find many of your skills transfer seamlessly. But, some things are very different, so let\u2019s dive in.<\/p>\n

The benefits of voice<\/h2>\n

As with any design it\u2019s best to ground the work in the value it can bring people.<\/p>\n

The accessibility benefits<\/a> to a person with a physical impairment should be clear, but voice has the opportunity to aid an even larger population. Small screens are hard to read with aging eyes, typing on a virtual keyboard can be difficult, and understanding complex technology is always a challenge. Voice is emerging as a tool to overcome these limitations, turning cumbersome tasks into simple verbal interactions.<\/p>\n

\"How<\/p>\n

As designers, we\u2019re often tasked with creating efficient and effortless interactions. Watch someone play music on a smart speaker and you\u2019ll see how quickly thought turns to action when friction is removed. They don\u2019t have to find and unlock their phone, launch an app, scroll through a list of songs and tap. Requesting a song happens in an instant with voice. A quote from one of our survey respondents summed it up perfectly:<\/p>\n

\u201cBeing able to talk without thinking. It’s essentially effortless information ingestion.\u201c<\/em><\/p><\/blockquote>\n

When is voice valuable?<\/h2>\n

\"When<\/p>\n

Talking out loud to a device isn\u2019t always appropriate or socially acceptable. We see this over and over again in research and real world usage. People are generally uncomfortable talking to devices in public. The more private, the better.<\/p>\n

\"Graph<\/p>\n

Hands-free and multi-tasking also drive voice usage \u2014 cooking, washing the dishes, or driving in a car. These situations present opportunities to use voice because our hands or eyes are otherwise occupied.<\/p>\n

But, voice isn\u2019t just used for giving commands. Text-to-Speech can generate content from anything written, including articles. It\u2019s a technology we successfully used to build and deploy Pocket Listen<\/a>, which allows you to listen to articles you\u2019d saved for later.<\/p>\n

\"Pocket<\/p>\n

In the graph above you\u2019ll see that people primarily use Pocket Listen while commuting. By creating a new format to deliver the content, we\u2019ve expanded when and where the product provides value.<\/p>\n

Why is designing for voice hard?<\/h2>\n

Now that you know \u2018why\u2019 and \u2018when\u2019 voice is valuable, let\u2019s talk about what makes it hard. These are the pitfalls to watch for when building a voice product.<\/p>\n

\"What\u2019s<\/p>\n

Voice is still a new technology, and, as such, it can feel open ended. There\u2019s a wide variety of uses and devices it works well with. It can be incorporated using input (Speech-to-Text) or output (Text-to-Speech), with a screen or without a screen. You may be designing with a \u201cVoice first mindset<\/a>\u201d as Amazon recommends for the Echo Show, or the entire experience might unfold while the phone is buried in someone’s pocket.<\/p>\n

In many ways, this kind of divergence is familiar if you\u2019ve worked with mobile apps or responsive design<\/a>. Personally, the biggest adjustment for me has been the infinite nature of voice. The limited real estate of a screen imposes constraints on the number and types of interactions available. With voice, there\u2019s often no interface to guide an action and it\u2019s more personal than a screen, so request and utterance vary greatly by personality and culture.<\/p>\n

In a voice user interface, a person can ask anything and they can ask it a hundred different ways. A list is a great example: on a screen it\u2019s easy to display a handful of options. In a voice interface, listing more than two options quickly breaks down. The user can\u2019t remember the first choice or the exact phrasing they should say if they want to make a selection.<\/p>\n

Which brings us to discovery \u2014 often cited as the biggest challenge facing voice designers and developers. It\u2019s difficult for a user to know what features are available, what can they say, how do they have to say it? It becomes essential to teach a systems capabilities but difficult in practice. Even when you teach a few key phrases early in the experience, human recall of proper voice commands and syntax is limited. People rarely remember more than a few phrases.<\/p>\n

The exciting future of voice<\/h2>\n

It\u2019s still early days for voice interactions and while the challenges are real, so are the opportunities. Voice brings the potential to deliver valuable new experiences that improve our connections to each other and the vast knowledge available on the internet. These are just a few examples of what I look forward to seeing more of:<\/p>\n