SwiftKey Flow beta now open
swiftkey.net
swiftkey.net
But coming out from under my tin foil hat (coincidently I just returned from a crypto-party at the Open Source Developers Conference), I don't trust proprietary keyboards which require internet permissions, because they have access to all of the passwords I type in. I've got DroidWall [0] denying internet access to it, and I can sleep easier at night. The only down side is I can't download new dictionaries if they become available.
[0] - http://f-droid.org/repository/browse/?fdfilter=droidwall&...
Edit: Specified why I don't like them having internet permissions
You could use Titanium Backup to back up SwiftKey, download the new dictionaries copy them somewhere safe, restore your files, than replace the dictionaries.
Someone else reported it, I and several others voted the bug, nothing happens. I still use it but now it may take days after a new firmware before I care to reinstall.
I have no idea why many companies don't release often.
I find that it wouldn't store words I've told it to remember and would constantly tell me they're misspelt, or it would remember bogus words and would continuously autocorrect them. Meanwhile, the stock Android keyboard is pretty nice, I don't know how long SwiftKey will continue selling when they are this sluggish.
On top of that, the "send feedback" feature on the mobile phone redirects you to a forum where you have to go through a lengthy registration process just to post something. I'm really disappointed and frustrated by SwiftKey's (nonexistent) customer support.
Of course, recently we've been using Whatsapp instead and that works perfectly fine.
That aside, SwiftKey isn't active on my devices either: It was really neat and got worse. It's technically unusable for my 'flow' right now and I see the same issue reported multiple times on their site. No fix. Keyboard that doesn't work as keyboard: Failed product. Adding a new way to input stuff while the current version is broken is a bad way to treat users..
One of the reasons why SwiftKey doesn't perform as well as it could for me might be that I use it with two languages, typing in each more or less 50% of the time. The fact that it can predict the next word based on the current one does help here in order to get the language right, but the three measly slots it has for word suggestions are still cluttered with words from the other language most of the time when I type. I think performance would boost if it could detect the language during the first few words and only suggest words in that language from that point forward. Then again, I often mix the two languages in a single sentence..
This, for me, is the killer feature of SwiftKey. I hate having to go into some settings panel and switch between languages each time I want to type something. I don't think I'd ever consider switching to a keyboard that didn't support this.
I've only tested it on my Nexus 7 but the swiping motions are very smooth and nicely decorated. The 'never lift your finger from the screen' thing works very well, and its genuinely a really pleasant keyboard to use.
It also still works like SwiftKey itself. Despite the opinions of many in this thread, I still consider it to be a a wonderful keyboard if you use it on a device that can keep up and you train it right. It really can make typing very fast with its excellent predictions.
The combination of the predictions with the swiping motion means it comes up with reasonable sentences rather than just relying on the individual words it thinks you typed.
Really? I can't get it to work at all. It looks like it tries to predict the entire sentence, and if it gets lost it just drops the whole thing. I would much rather it spit out a word each time I swipe down to the spacebar, that way if there is a prediction error I can stop and correct that word without losing an entire sentence.
For example, it sometimes gets my HW keyboard state reversed (when I slide the keyboard out, the on-screen keyboard appears, and when I retract it the on-screen keyboard disappears).
It's also completely unusable with firefox.