For those of you attending my talk tonight, this is a great example of a potentially good product (high utility) and poor experience. Later in the thread, @BrianRoemmele indicates that there have been updates, but really there is no good reason to deploy a #voice UI like this.https://twitter.com/tomfgoodwin/status/844692158930190336 …
Phillip, thank you. I see your perspective. I do have a question. When you go into a sandwich shop or burger or pizza place. How do you order your food? What interface do you use? What is the interaction?
-
-
A good voice interaction can be a great experience for this use case. Utility & convenience potential is high. The UI I heard could've capitalized much better on those traits. That UI offers a flow completely different from typical menu+phone routine, and is overly interrogatory.
-
Phillip, indeed I fully agree. Again this demo was a few days after the first ASK system was released. It had significant limitations. Yet, the hotel chain liked it and had courage to test. They will be the first to capitalize on this feature deploying it in 1000s of rooms.
End of conversation
New conversation -
-
-
Phillip, to be clear. This was an alpha version of a skill designed 3 days after skills were released by Amazon. The hotel that is testing version 19, in Las Vegas has processed 1000s of food orders using this system. There have been no complains and high reuse.
-
That's great. I was specific that the version shared had poor UI. Glad to hear about improvements. Low complaints aren't surprising. Customers frequently blame themselves or are ignorant of how UI could be better. Speech ux has mostly sucked, so why expect different?
- 2 more replies
New conversation -
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.