| |
  |
| Comparing Voice User Interfaces with GUIs |
|
 |
|
posted by Editor on Monday January 05, @11:03PM
|
|
|
|
|
This article on informit.com compares Voice User Interfaces (VUIs) with Graphical User Interfaces (GUIs), and identifies some of the functions that VUI designers need to address to support basic tasks such as web surfing. The article points out that VUIs are invisible, single-mode, task-focused, and are usually deployed in environments that compete for users' attention and cognitive processing. Since there are no standard VUI equivalents for GUI browsing functions such as "home", "back", error dialogs, or online help, each of these must be reimplemented by VUI designers, along with their corresponding functions. For example, a VUI might have two notions of "home": returning to a voice portal, or "starting over" to return to the starting point of the application.
|
|
|
|
< Telepresence Via Zoetrope | New User Interface Environment Has No Boundaries > | |
|
|
|
Don't have an account yet? Go Create One. A user account will let you customize the site's content according to your preferences. It will also allow you to moderate the comments of other users.
|
|
|
|
|
|
This discussion has been archived.
No new comments can be posted.
|
|
|
|
|
by Anonymous Coward on Tuesday January 06, @06:01AM EST (#1)
|
|
|
|
|
They really don't know what they're talking about if they try to draw a parallel between a VUI and a GUI instead of a CLI. And their first bullet point is way off the mark from that perspective, because the big advantage of a command-based (be it typed or spoken) is that you can know things globally and do modeless processing. By going a "lightest possible demands" route, you completely remove that advantage.
I use the voice recognition system on my Mac for a small amount of things, but in almost every case those things are open-ended, such as switching to an application that isn't readily available in "hot spot" with the GUI; that is, instant access to hundreds of apps "memorized" by name without having to click around. If you restrict me to a system that forces me to do voice navigation the same way I'd do graphic navigation to find/launch an app, you'd take away a big win that a command-based system gives.
So everyone doing voice should clearly be taking their hint from shell development of the past, not the GUI development that followed it. This article is a bit dated, though, and the book it references is already out of print. I imagine more sensible directions have been taken in the last 2 years.
|
|
|
|
|
|
|
