One of the biggest problem facing voice interaction design today is the framing of voice interfaces as “assistants.”
-
-
Replying to @maryparks
Mary, indeed! The issue is complex today but normalizes over time as the endpoint is a true Personal Assistant. Not seen in current systems.
1 reply 0 retweets 0 likes -
Replying to @BrianRoemmele
The assistant metaphor overall is not useful nor desirable. It negatively constrains the set of design possibilities and desired outcomes.
4 replies 0 retweets 1 like -
Replying to @maryparks @BrianRoemmele
2/2.But I do believe that the framing biases for functionality, when we want more from our Alexa than mere assistance: e.g., companionship
2 replies 0 retweets 1 like -
Replying to @didou @BrianRoemmele
Beyond the biases, the framing of voice UIs as “assistants” has created a mess of fatal inconsistencies in voice UX.
2 replies 0 retweets 1 like -
Replying to @maryparks @didou
Mary, indeed. The difference is profound and hard to roll back. Good design would have solved expectation issues.
1 reply 0 retweets 0 likes -
Replying to @BrianRoemmele @didou
No need for the past tense. I have a hunch the use of “assistant,” both as design metaphor and as shorthand for voice UIs, will end.
2 replies 0 retweets 1 like
Mary, indeed. Coupled with design that elucidates abilities and limitations clearly.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.