31–40 of 122 posts
Technologies used for a static list (!): react redux reselect aphrodite material-ui stylz redux-form react-helmet webpack faker lodash moment
Is anybody else having trouble using Ok Google for sending texts? It recognizes the recipient alright but stops dictation way too early, even if I pause just for a second. Then it doesn't seem possible to resume dictation. Does anybody know how to get around this? (Android 5.1.1)
A small typo I noticed is under "Device Control", an option is "Turn on/off Flaslight" rather than "Flashlight"
I used to love using the "remind me to" command. It was a fast and convenient way to set alarms. Recently, when I attempted to use it on iOS, I was hit with an alert that "reminders have been moved to the Calendar app," where it is far less convenient to set up a reminder. Instead of just setting the alarm with my voice and then confirming it, I have to use a click wheel to set the time, and it takes like three more…
Is that an iOS thing? On Android reminders through the Google Now interface seem to work fine.
I think this is great, and at the same time highlights a usability problem with conversational interfaces: we don't know how to make them discoverable. Google attempts to do this by letting you stumble upon commands, but I don't think that is good enough. I don't think tutorials are either, but I don't have any solid alternatives.
I think this is great, and at the same time highlights a usability problem with conversational interfaces: we don't know how to make them discoverable. Google attempts to do this by letting you stumble upon commands, but I don't think that is good enough. I don't think tutorials are either, but I don't have any solid alternatives.
I used to love using the "remind me to" command. It was a fast and convenient way to set alarms. Recently, when I attempted to use it on iOS, I was hit with an alert that "reminders have been moved to the Calendar app," where it is far less convenient to set up a reminder. Instead of just setting the alarm with my voice and then confirming it, I have to use a click wheel to set the time, and it takes like three more…
I think this is great, and at the same time highlights a usability problem with conversational interfaces: we don't know how to make them discoverable. Google attempts to do this by letting you stumble upon commands, but I don't think that is good enough. I don't think tutorials are either, but I don't have any solid alternatives.
How about, when you perform an action manually it says "by the way, in future you can just tell me to ..."
If I also use something that doesn't have a shortcut 3 times within the programs running then it asks me if I want to set a shortcut for that action.
I think as time goes on Google will eventually be on this route considering how well it works (at least with the first portion of showing the shortcut command whenever I use it).
However that still wouldn't solve the problem of the users having to learn the commands from scratch first so if they don't know it exists they would never learn the shortcut for it in "OK Google"