So, it's interesting. I resisted the iphone-style smartphone for a long time (I loved my nokia communicators) - I mean, I was super into wearable computers; I owned an Xybernaut at one time; I had the palm v with the cdpd modem... but I resisted the winning form factor for so long.
And... yeah, it was a mistake. Not really a huge one, 'cause the things are designed to be easy to learn over being easy to use (there's usually an either/or there. the easiest to learn process is rarely the most efficient process) but still, a cost; to this day, I'm not all that great at typing long messages on a phone keyboard, like young people seem to be. For that matter, I didn't buy a car GPS until far after they were common, and I am unusually bad at reading maps for a man who started driving before consumer GPS was common, so I would have saved many hours and more than one job interview if I had that technology sooner.
I kind of feel the same way about voice control. I mean, essentially it's a command line interface with a wonky input method, no? and it's a command line interface designed for regular people, not people who are familiar with the command line tradition. I don't think it's super useful now, and I kinda think it will be a fad, like the '80s talking cars.
But, I could be totally wrong. What am I missing out on by resisting the voice controlled garbage?
I mean, if someone does come up with a google maps level 'killer app' that makes you way more effective if you use the voice control, I'll be behind the curve.
"I mean, essentially it's a command line interface with a wonky input method, no?"
This is precisely the feedback we got from salespeople, when we were working on a Natural Language Programming interface for Salesforce. Initially, I got angry and denied the comparison. But after several people made the same comparison, I came to appreciate how true it was. Unless NLP is perfect, it is really just a Command Line Interface with an awkward input device. I talk about this a little towards the end of this story:
https://www.amazon.com/Destroy-Tech-Startup-Easy-Steps/dp/09...
The privacy issue is easily solvable IMO. Google already requires a physical mute button on their devices to disable the mics in hardware not just software. It will require either user trust (admittedly in short supply with tech companies lately) or some government regulations but there is no reason even today for devices to have to "record" your conversations in order to process. As long as you require a "wakeword" to tell the device to start listening to your next commands the device doesn't need to record all audio all the time.
Avon
IBM
Sinopec
Volkswagon
Alexa could not get these, which made the skill nearly useless.
It is much easier to simply use a keyboard.
And please consider the failed promises we've heard over the last 3 years. Remember "Invoxia will enable Alexa to tell which person is talking":
http://www.smashcompany.com/technology/invoxia-will-allow-al...
One as limited options in terms of forcing Alexa to pause in certain parts of a word:
http://www.smashcompany.com/technology/using-a-glottal-stop-...
I wrote this when I was still optimistic:
http://www.smashcompany.com/technology/how-to-build-conversa...
Please elaborate. What do you mean by "thousands of hours of learning". Aren't you overplaying it to fit your narrative?
Have you ever done IT for your family or friends, or seen a coworker completely helpless in the face of an unrecognized file extension? Say they're, I don't know, an engineer or a call center operative or something. 6 hours of computer in a working day, 250 days of work a year, maybe they got out of college in 2005... more than fifteen thousand hours in front of a computer, and, well, https://www.youtube.com/watch?v=fa9DLxDtPtc. Computers are mindbogglingly complicated.
And then there's us, the people that hang out on HN. I can't even think of how many times I've spent fifteen minutes digging around in config files or menus or googling for a better tool. I've probably spent over a hundred hours just on my emacs setup. Easily hundreds, perhaps thousands, of hours of focused effort dedicated solely to high-end computer-use skills, and that's not even counting the things I use the computer for. And I'm still learning things every day.
> Now try teaching a non-technical user about cron, its flags, and its relationship to other shell commands, using natural language.
I'm just not sure what you mean with this statement. Are you talking about setting up cron jobs via voice? Or are you just making an analogy about the (perceived?) complexity of cron and teaching it to a non-technical user?
"Please remind me every day at 5pm to water the plants", or "Please play this song at medium volume every morning at 7am"
than to learn how to do the equivalent in whatever operating system their device uses, and I'd tend to agree. Cron is certainly a much higher bar than learning to use the alarm app in your phone, but the point remains, particularly in a home context.
I mean you can use the GUI (launching apps etc.), or literally just type "remind me every day at 5pm to water the plants" into the home screen search bar (on Android at least).
The voice recognition and the assistant parts are decoupled.
I taught one of my family members about using PC and Android, and found that almost everything needs to be explained. For example: - What's Google/Microsoft for? (Yes, even the giants in tech may never be heard for some people and it's common) - Browser? And there are many of them? (Not everyone has a computer and Internet access) - URL? What is that? I cannot even spell it! (This is more complicated and requires people to remember the addresses of tens of commonly used websites, btw, what's a bookmark!?) - register? with what? bank account or passport? (if someone doesn't have a email account, it's likely that they have no idea about the process of register, activation.) - App market? wait a second, what's an app? (not to mention built-in ones and those from 3rd parties)
The thing is Alexa, google home and many others provide a unified, easy to use substitute(well, I have to admit these devices are pretty dumb these days. So they are not 100 percent alternatives). The only requirement is being able to speak in a clear way, which is true for almost everyone.
PS: I don't have any of these devices. As a hard-core programmer, my choice is, without any doubt, *nix, shell, etc. GUI sucks ;-)
Are you saying that voice UI is not its own "application context"?
It's an undiscoverable mess.
I can type everything I'd issue as a voice command into my home screen. I have to install and learn just as few/many things and commands as I'd have to using voice recognition. Op might have underplayed something, you just made things up.
You are not the market that these are targeted at then. The normal person cannot do those things.
You're underplaying it in order to artificially inflate your mileage.
Having a voice assistant means not having to learn to change application contexts inside an operating system follwed by a few seconds typing. You are ignoring the hundreds/thousands of hours you've spent learning which software is appropriate for which contexts. Not to mention the latency of instantiating them, or possibly even installing them, migrating data between them, etc.
Voice assistants have contexts but they map fairly closely to natural language. And non-technical users can teach other non-technical users what those contexts are. "Here's how you set an alarm." I've never used Alexa but I'd bet it's something like, "Set an alarm for blah," or even, "Wake me up at blah." And I bet if I asked an Alexa user how to do that I'll remember because it's all natural language. That's a huge win for usability.
Now try teaching a non-technical user about cron, its flags, and its relationship to other shell commands, using natural language. In a decade that bullshit will sound more antiquated than the amplitude modulation on the voice of a Dalek.