Shared publicly  - 
Here's a feature I desperately want in Android.

Sure, I can select my own favorite keyboard to use, like SwiftKey and Swype. But voice entry is tied to that choice.

The problem for me is: I LOVE SwiftKey 3. Love it more than even the improved keyboard in Jelly Bean (though the stock keyboard has really come a long way.) But I don't allow myself to use SwiftKey 3 currently. Cause then I'm locked into also using SwiftKey 3's speech-to-text system. And if you haven't noticed, Jelly Bean's speech-to-text is the bee's knees, IMO. SK3's is ok. But doesn't include things like JB's "type as you talk" function that I find incredibly handy. I use speech-to-text enough for this to actually keep me from switching over (right now).

Please give me the ability to choose a keyboard AND choose voice input. They shouldn't have to be intrinsically tied together.
Jason Howell (raygun01)'s profile photoBrad Schroeder's profile photoKaarel Kaljurand's profile photoVance McAlister's profile photo
Couldn't agree more. Really I just want to know why the JB keyboard on my Galaxy Nexus has long press for numbers and that ability does not appear using the same keyboard on my Nexus 7. VERY ANNOYING!!!
Absolutely. I have this exact same issue. 
+Jason Howell OK, here is a workaround I figured out.  When SK3 comes up, pull down the notification bar, tap "choose input method", tap Google Voice Typing, it will start the awesome ICS/JB voice dictation, and enter it in the field.  When done, SK3 will still be there as your keyboard.  It is a couple of extra taps, but well worth it to use both the superior SK3 keyboard and the superior Google Voice Typing.   The folks at SK were pretty stoked about this workaround when I presented it in the VIP forum and are recommending it to folks until they get things worked out (they ARE working on it).
 +Lance Burkhardt  They have assured us that they are working on it.  The problem is getting it to work without messing things up for the 90% that don't have ICS or Jelly Bean. 
exactly how I think. I love using Swiftkey, but the voice typing on the stock keyboard is amazing! I love how it types as I talk. The Swiftkey one runs just like the apple one...
I had been thinking of putting Swiftkey on my Nexus 7 - maybe I won't for now. 
I asked this question somewhere around the time +SwiftKey 3 was released, and as I recall, the response was that the Google speech-to-text was it's own IME and that they'd look into it if enough of their userbase was interested. I wasn't clear whether this input had to come from their VIP forums or the community at large.  +Jason Howell , I think you have the clout to get this going!

#swiftkey   #featurerequest    #useyourvoice  
I agree. But, we're so spoiled. Apple doesn't even allow alternate keyboards :)
+Raul Hurtado I think we're only "spoiled" if we whine about it... Asking should still be okay. ;-)
There is also a place where you can "vote" for this feature to be added on their support site.  They already have it under consideration and know it is a significant issue, but every vote helps, I am sure.  In the meantime, I have gotten used to the workaround I described above, so it is not a big issue for me.
I agree, but it should be an option, for me I am on the original Droid X with no hope of JB. I use swype because the voice dictation built in to swype is far better than Gingerbread's voice to text. 

If I could choose SK3 for typing with Swype's voice I would be loving it. 
LOL - but i agree, any third party keyboard should be able to use Jelly Beans voice control, it should, and they should make it happen! :-)
I am in the same position except with Swype. I like using Swype on occasion but would still like to be able to use the Google voice to text.
I totally agree, but I personally can not get myself to abandon SwiftKey 3. It works so good and has such an awesome design that I just can't leave it. Not I big user of speech to text though so I guess it's not as big of a deal for me to choose it over stock. After reading this post though I think I might check out stock and experiment with 'Type As You Talk' a little tonight.
+james whelan  Just a reminder, you can check out the "type as you talk" without switching to stock, just try the workaround I describe above.
+Vance McAlister I used that method for a while, but the annoyance was just too great for me. IIRC anytime I tried to correct what the dictation got wrong, it would revert to SwiftKey. So, when posting a long message, I would have to use the workaround 3-4 times. In the end, I just quit using it and do without dictation (or use SwiftKey's internal one). Hopefully +SwiftKey can get the stock one working.
Very true, you really get one long shot at it. I just wait and do any corrections after I am done. The good thing is that you can pause all you want along the way. But corrections have to wait.
I don't use voice, but I would love for an easy way to switch keyboards, or assign per app.  For most apps, I like a predictive keyboard (I'm using Swype), but if I'm in a terminal app typing Unix commands, I would prefer a regular not-fancy keyboard.
This was discussed frequent on SwiftKey's forum during the beta. I'm sure they are doing everything in their power to make other happen. Thanks +Vance McAlister for the workaround. Didn't realize you can pull down the notification bar for the keyboard option and the long press for input method seems to be gone.
Question for you and the rest of the AAA Crew. Received my Nexus 7 on July 17th, enjoying the experience but noticed a possible manufacturing problem, it does get warm to touch, it appears that the touch screen was uneven on left side of case/bezel, I am always applying slight pressure to place it even with the edge. I am concerned that this might allow humidity to enter the unit resulting in some type of failure. What do the AAA Crew think?
+David M. Dwight You really shouldn't hijack posts. Try posting to your own stream and mentioning +Jason Howell and +All About Android in the post.  They'll get notified that you mentioned them. (Or you could send an email to and have your question read on the air!)
Totally agreed. I'm still using SwiftKey though because I type more than I talk.
Hi Jason. I agree with you whole heatedly and have felt this way since I of my VZW galaxy nexus on launch day. Last week I uninstalled sk3 after having unprecedented bugs since last update. Not just me not just one device. Put jb keyboard app on my phone and got nexus 7 and have not looked back....well maybe a little.
Just got around to seeing this weeks episode.  Thanks for the tip on using the google voice input w/swiftkey.  Fantastic Tip
Hey Jason, long time listener, first time caller.  I love Swiftkey 3 but also find the Google Voice Typing extremely useful at home.  I found a solution that works really well for me and consider it a must share.  To make the transition even better, I setup a task in Tasker to switch the default keyboard for me.  I also use an app called SwipePad which I think you guys have reviewed in the past.  It is very quick to switch and whenever you're done, it goes right back to Swiftkey 3 as your default.  Here is a quick video of it on my phone (Tasker SwipePad Change Input). I don't think you can switch between keyboards any quicker than that.  If you have any questions on the setup, let me know.  Hope this helps.
SwiftKey currently uses Android's standard RecognizerIntent-API (which has been around since Cupcake) to connect to the speech recognition provider. This is a flexible solution which allows third-party app developers to provide their own speech recognition service on Android, e.g. the Estonian speech recognizer was made available on Android this way. (Important to note: Estonian is a language with 1 million speakers, the smallest languages that Google's speech recognizer supports have 10 million speakers.) I've seen keyboard apps recently (on ICS) where the microphone button directly launches  Google's new voice typing IME. So the user is basically locked into using the Google product, with all its awesomeness, but also its limitations (e.g. choice of languages). Hopefully SwiftKey can come up with a solution which allows the user to configure which recognizer the keyboard is connected to (ideally informed by the current keyboard layout language).
+Kaarel Kaljurand That is great information!  Which app was it that directly accesses the voice typing? Swiftkey was asking if there are any third party apps that did this so that they could figure out what they were doing.
+Kaarel Kaljurand  That is very cool, thanks.  What Swiftkey is particularly trying to figure out is how to enable the Voice Typing for ICS and Jelly Bean phones from their keyboard while still allowing for their own voice input from older phones, without having to create two different versions.  Sort of a toggle or option.  I wonder if anyone has been able to do that in particular yet, using both the Voice Typing and a proprietary option at the same time.  
Add a comment...