Hey Androiders,
So I've been a bit of a fan of voice operation since I was about 15. I'm pretty pumped about Voice Search on Android ever since it came out. I've tried oodles of different voice operation software - some of it is more versatile than Voice Search, but none are as fast - which I think is the whole point. I am a VZW sales rep it has really helped me get a tonne of folks into Android phones vs iPhones (or basic phones) because of it's speed with basic actions.
To me, if it's not fast - it's not functional. Otherwise you're just conversing with a piece of aluminium and glass - and that's when things get hairy and they call the men in white coats.
I was even excited to test out *gasp* Siri on iOS6 on iP5- I gotta say - speed and versatility - really not bad at all.
So I was really excited to test out the new JB voice actions. It was a bumpy ride at first, but after uploading JRO030, things are looking much better - but still not quite as fast as ICS. (get it here: Want Jelly Bean JRO03O for the Verizon Galaxy Nexus? | Android Central ) I gotta thank Mac58 again for pointing out to my dumb ass they latest build...
I finally got my hands on a phone to record a speed test between ICS and JB - and I think ICS still edges over a little faster just a little bit. Nothing to write home about, but faster none the less.
What I've found it isn't the speed of the action that slows it down so much (although it does), but the specificity required for the action to successfully complete that slows it down. Significantly more information is required for a successful action, which isn't always available to the user at the time of creating it.
If you had two guys with phones in their pockets - guy A has ICS, and guy B has JB - and asked them to perform the same action; Guy A has the advantage because less information needs to come out of his big, dumb, pie hole.
Don't believe it? Try it yourself by copying one of my demo commands if you're running JB - "Call Pro Cellular in Black River Falls", will bring up a map, whereas "Call Pro Cellular, on Main Street, in Black River Falls" will initiate the call. Seems funny to bring up a map when the command was initiated with the word "Call" . The map is pretty, but that's what "Map of" command is for.
There are other examples of this, that you can see in the vid - but it makes you wonder where Google is going with this? If we're going to see Google Glass in less than 6 months, and Google is committed to creating devices/programming that is designed to keep tech OUT of our lives so as to get on with life - why the nudge to requiring more information to create a voice command? Personally it doesn't feel like a step in the right direction.
I am PUMPED to see Google Glass go mainstream (if they created a lotion filled with Nanobots that crawled into your neocortex and allowed access online I would volunteer myself as a guinea pig in a heartbeat) - but why more information required, Google? It seems counter productive to Google X Labs, and a step backwards from ICS' (and GB for that matter) fast, non-intrusive, extremely useful set of commands.
If Google Glass is running KLP, or I dunno...LCT (Lemon Cream Tart) - I hope they either A) realize the speed difference, or B) give me the option to flash ICS voice operation on it.
Ics vs Jb voice search/actions - YouTube
So I've been a bit of a fan of voice operation since I was about 15. I'm pretty pumped about Voice Search on Android ever since it came out. I've tried oodles of different voice operation software - some of it is more versatile than Voice Search, but none are as fast - which I think is the whole point. I am a VZW sales rep it has really helped me get a tonne of folks into Android phones vs iPhones (or basic phones) because of it's speed with basic actions.
To me, if it's not fast - it's not functional. Otherwise you're just conversing with a piece of aluminium and glass - and that's when things get hairy and they call the men in white coats.
I was even excited to test out *gasp* Siri on iOS6 on iP5- I gotta say - speed and versatility - really not bad at all.
So I was really excited to test out the new JB voice actions. It was a bumpy ride at first, but after uploading JRO030, things are looking much better - but still not quite as fast as ICS. (get it here: Want Jelly Bean JRO03O for the Verizon Galaxy Nexus? | Android Central ) I gotta thank Mac58 again for pointing out to my dumb ass they latest build...
I finally got my hands on a phone to record a speed test between ICS and JB - and I think ICS still edges over a little faster just a little bit. Nothing to write home about, but faster none the less.
What I've found it isn't the speed of the action that slows it down so much (although it does), but the specificity required for the action to successfully complete that slows it down. Significantly more information is required for a successful action, which isn't always available to the user at the time of creating it.
If you had two guys with phones in their pockets - guy A has ICS, and guy B has JB - and asked them to perform the same action; Guy A has the advantage because less information needs to come out of his big, dumb, pie hole.
Don't believe it? Try it yourself by copying one of my demo commands if you're running JB - "Call Pro Cellular in Black River Falls", will bring up a map, whereas "Call Pro Cellular, on Main Street, in Black River Falls" will initiate the call. Seems funny to bring up a map when the command was initiated with the word "Call" . The map is pretty, but that's what "Map of" command is for.
There are other examples of this, that you can see in the vid - but it makes you wonder where Google is going with this? If we're going to see Google Glass in less than 6 months, and Google is committed to creating devices/programming that is designed to keep tech OUT of our lives so as to get on with life - why the nudge to requiring more information to create a voice command? Personally it doesn't feel like a step in the right direction.
I am PUMPED to see Google Glass go mainstream (if they created a lotion filled with Nanobots that crawled into your neocortex and allowed access online I would volunteer myself as a guinea pig in a heartbeat) - but why more information required, Google? It seems counter productive to Google X Labs, and a step backwards from ICS' (and GB for that matter) fast, non-intrusive, extremely useful set of commands.
If Google Glass is running KLP, or I dunno...LCT (Lemon Cream Tart) - I hope they either A) realize the speed difference, or B) give me the option to flash ICS voice operation on it.
Ics vs Jb voice search/actions - YouTube
Facebook
Twitter
Instagram