Slashdot Mirror
Google Drops Desktop Voice Search In Chrome (google.com)
PC World reports that even as Microsoft is pushing voice input on the desktop (in the form of an expanded role for its Cortana digital assistant), Google is responding to user (dis)interest in searching by voice from the desktop, by dropping "OK Google"-based voice commands in the latest iteration of Chrome. This seems too bad to me, so I wish they'd at least leave the voice input as an option; I've only lately been getting comfortable with search by voice on my phone, and though I've found the results to be hit or miss (my phone responds a bit too often to "OK," and seems to stumble even on some common words, spoken clearly), when it works I really like it.
Voice search on the phone is natural. The phone is a device that historically is good at one thing, voice. Even though a modern phone has a decent keyboard input, t's still clumsy when on the go. When I'm out for a run or a ride and I want quick directions, or to dictate a note, send a text message, or check the train schedule, the voice interaction is vastly superior to wrestling my phone out of it's armband and typing something. The voice interaction isn't amazing, but it works about 80% of the time on the first try and that's good enough for me. I don't have to stop my workout and fumble around.
On the other hand, when I'm sitting at my desk I can, with two key strokes switch to my web browser and launch a new search tab. I can type about as fast as I can speak and my accuracy is probably around 95%; google makes up for the remaining 4% in spelling errors (searching for instead of ). I get better accuracy and less fumbling around if the room is loud. Also, in our quiet open-plan office I look like a total D-Bag talking to my monitor. That's a big plus. too.
The full-size keyboard isn't the end-all of interfaces, but for a desktop it's waaaay better than voice search. If voice search ever gets to the point where I can throw out a complex, natural language queries into the air a la ST-TNG, I'll switch. "Computer: Post a witty comment to SlashDot about voice interfaces and how bad they sucked in the naughties and teens"
This one's tricky. You have to use imaginary numbers, like eleventeen... --Hobbes
I'm sorry Dave, did you say "OK Google, NSA?"
Mod me down, my New Earth Global Warmingist friends!
Some disabled people are going to be very sad
If you are disabled enough to require voice control over your computer then you probably want to operate more than just Chrome and will have some more system-wide software in operation. It won't make much difference to them (in fact, it may be better as you don't have two different systems trying to listen to your voice).
There might be disinterest because it was a 'hidden setting' (at least for the longest time). I know I wasn't using it because it stopped working for no reason about two months ago. I assumed they just broke it like they do the rest of their stuff every time they touch something and force the update, or discontinue something I found useful. Forgive me while I rant for a moment...
These days I don't invest any time in anything Google does because I know it's going to be perpetually half broken until the day they silently drop it or decide to screw it up a la Maps while the community screams at the top of their lungs that the new version is shit. My theory on Google is that it isn't run by software engineers and sysadmins anymore, but rather by UI and UX focused kids straight out of school.
I have patches in the Linux kernel and I can't freakin' figure out how to send a text to a person I know since they mangled Google Voice into Hangouts. As an added bonus, when I send a call with Google Voice it no longer allows me to, you know, select which phone it should call me on - that's exactly half of the dialer's job and they couldn't get that in the product requirements apparently. I get more angry every time I log into voice.google.com to set which phone to call and there's a banner across the top that reminds me that I should use the Hangouts interface for using Voice. This is the quality of engineering left at Google.
My final "no shits to give" moment was when they discontinued the NaCL plugin architecture in Chrome with a smug "we told you a long time ago we were going to do this, you should have migrated your stuff." To which I wanted to wipe the smug away with a hammer while shouting "I didn't write our hardware vendor's frakkin' web client, I can't rewrite it and we need to be able to access IPMI interfaces for hundreds of boxes out in the field!" Needless to say, we're transitioning away from our Enterprise Google Apps/Docs/Domain account back to Microsoft (again). Those stories aren't related in any way other than I didn't bother putting up a fight when we were acquired and it was decided we'd use MS Office - I suspect I'm not the only one that didn't want to burn political capital on Google.
If I mod you up, it doesn't necessarily mean I agree with what you've said, sorry.
This is why Google needs to collect MORE data on my browsing habits - after a few weeks of grab-my-dick-'n'-double-click it knows exactly which midget clowns will most titillate me. Hell, it could pre-empt the times of day I'm likely to spank the monkey and be all, "Dave, your midget clown porn is ready for your regular morning meat-beating." It'd even know how quickly/slowly I like to browse through the pictures. I'd have to give it some sort of exception to the appointment like, "OK, Google, when my mother-in-law visits, ixnay on the idget clown pornmay." and if it isn't sure who my MiL is I can tell it to monitor my Fitbit for signs of severely increased blood pressure and dread.
Meanwhile, Microsoft would have a Clippy pop up on the screen and ask, "It looks like you're choking the chicken - would you like some help gripping that?" and before I know it a wiry piece of metal is wrapped round my John Thomas, grazing it to buggery, and I'm begging for forgiveness for all the times I made fun of people for suggesting it's time for Linux on the desktop.
The future is now!