Our sense is that people don't want to use speech for everything ever, they'd much rather use their hands and eyes when they're available. We're laser focused on texting while driving right now, it's the one big use case for voice commands.
We've done a lot of user testing and have found the biggest problem with voice products now is that people try them twice or three times, and when they don't work they decide to give up on using that product. No one wants to spend time learning a user interface. So we've optimized our product for the first time user experience for texting. We're offering what voice what Dropbox did for cloud storage. There's nothing novel technology wise per se, only that the product is optimized for ease-of-use.
With regards to Siri, we're interested to see how it'll perform once it gets released into the wild.
We're laser focused on texting while driving right now, it's the one big use case for voice commands.
Regardless of whether your app is same/better/worse than Siri, please please please don't pursue a use case around texting while driving.
I'll skip my rant about the fact that texting while driving is dangerous even if you remove the keyboard input (you still gotta read the reply messages @ 65mph).
(EDIT: Ok, I see that your app will read texts too. Still doesn't negate the following:)
The issue you face is that as a second-class citizen app (ie not Google or the device manufacturer) on my phone, here is my workflow to text while driving using your app:
1) I decide I want to text
2) While driving, I have to feel my way around my phone to press the fiddly "power" button at the top of the handset (let's assume it is in a cradle)
3) Oh, but wait I have screen-wipe security enabled, so I now got to dance my finger across the screen - again, while doing 75mph (yes, I like to drive fast up the 280)
4) Ok so now I'm in. But damn, I'm at the home screen. I got to find your app - we'll assume I put it on the backdrop of the home screen. I press it and wait for the app to load.
This all assumes that I put your app in a primary positon on my phone, that I wasn't already in another app and so I had to press the home button, that the home screen wasn't on a different 'pane' then the one your app icon is on, and that your app starts recording voice commands as soon as I open it up.
Sorry, but that's still A LOT of steps, is dangerous, may not be legal in California due to it being more then one button and makes a lot of assumptions.
Google and the handset manufactures, who give themselves first-class citizen access, have the advantage because they can add extra buttons for one-press access. They can also use private APIs to potentially remove the screen lock (although that has other issues associated with it). Apple, when they integrate Siri into iPhone 4S, will presumably have similar advantages.
Sorry, I'm all for the little guy and the 3rd party ecosystem - but I'm also for safety. As a driver (and motorcycle rider) I really fear people using tools like yours while driving.
For that reason, I'm sorry, but I really hope your app is a failure.
We agree with you completely, we are very much for safety.
We are against people touching their phones while driving (it's illegal in most states) and designed our product specifically so you don't have to touch your phone.
It auto starts up when it detects you've begun driving via your speed from GPS (go to Settings in the app to enable the auto start up). We also designed this GPS detection to not suck battery life (it will take about 1% of your battery every hour).
It works on phones even if the phone is in the passenger seat next to you- you just have to make sure to talk loudly enough.
It will even pick up your voice if your phone is in your pocket (again, just speak loudly enough) and you can hear it talk back to you.
No touching your phone or taking it out of your pocket required.
edit: also, no need to downvote this guy, it was an honest misunderstanding.
If you have the "turn-on when driving" setting enabled, then our app will acquire a CPU wake-lock that keeps it running (this is not a big drain on the battery, about 1% per hour). Every three minutes we'll poll the GPS to see if you're driving and then start the application up if GPS indicates your speed is above 10mph. When it starts up it'll also notify you that it started up by speaking aloud to you.
If your phone is entirely off (and not just sleeped/screen locked) then there's nothing we can do about that... :)
Also if you have more questions, start a new comment thread in this post- the reply timeout makes replying super slow.
We've done a lot of user testing and have found the biggest problem with voice products now is that people try them twice or three times, and when they don't work they decide to give up on using that product. No one wants to spend time learning a user interface. So we've optimized our product for the first time user experience for texting. We're offering what voice what Dropbox did for cloud storage. There's nothing novel technology wise per se, only that the product is optimized for ease-of-use.
With regards to Siri, we're interested to see how it'll perform once it gets released into the wild.