Finally – I think I’ve discovered a better way to compose my blog entries safely while I am commuting. Last Fall when I started a new job in San Francisco and had to start commuting, I had the bright idea to compose my blogs with a Speech to Text App. I tried the speech to text app on my prior phone, which was Voice2Note and I tried others, including Dragon Naturally Speaking. However, what I said into the phone is NOT  what came out as text. The text message came out with something completely different. I had a 30 second clip using Voice2Note:

What I said: Concussions are a sneaky thing. Three of my kids played football and I have seen many concussions over the 4 years that we’ve played football. My son Jasper had a concussion last year and it caused nausea, dilated pupils, headaches, ongoing headaches; all symptoms that aren’t good. This year I’ve seen 4 kids on his team, these are the 13 and 14 year olds, …

[Note: the phone cut me off and I tried several more times, but this was the only snippet that was translated.]

What came back:  (?) my son Jasper has a concussion last year cause nausea dilate pupil headache on going head ache ongoing symptoms. 
Converted by: Voice2Note

Not even close… that question mark was a big question mark… and the rest of the text that was transcribed wasn’t even close either. I tried it for texts and IMs and it worked better than a rambling blog entry type transcription. But none were worth exploring further.

Now that I have a phone with Siri on it, I’ll try that feature and see how it goes. This blog on ZAGG points to one users experience using Siri to compose blogs. That one fared a lot better, which gives me a little hope, well, enough hope to try it again. I’ll try it out and report back on how Siri fared in blog writing/composing. It certainly can’t be worse than the last attempt!