Swiftkey 3 Updated With Jelly Bean Compatibility

• Haven’t looked back at Swift Key ever since they screwed up with their beta 3 “redesign”. It’s actually become less functional than some of the other knock offs in the market. 4.1 JB keyboard FTMFW!

• is the update available through the amazon marketplace? i got it from there when it was on sale but no update for me.

  • It took a couple extra days but I saw the update.

• Can someone please explain to me why swiftkey is so good? whenever I try to use it it picks up about every sixth keystroke. Swype has always worked very well for me.

  • I don’t see the big deal, either, but I’m also a Swype user (and it’s really hard for me to go back to pecking away at the screen).

• first app i bought yesterday when i got my nexus 7

• Since when is it not compatible with JB? I’m running Rootz right now with it installed….

  • it says the update makes it fully compatible…it doesnt say it never was compatible

    • *shrug*

      Never had an issue with it. I like to see updates, though so…no big. 🙂

      • which was exactly my point…updates are always good, especially if they allow even a random minority more complete access

• is the same version available on the Amazon market??? (i got the free copy there)

• HELL YES!

• Does this correct the auto correct bug that auto corrects to words that do not actually exist if you hit the first letter wrong? gerro, ketter, etc….

  • i’ve had it correct my correct spellings to non-existent words

  • mine red underilines words that are spelled correctly almost like it is a grammar error when it is not. But the predictive text is better than ics , but on the stock browser using stuff like dicus it has problems recognizing what i’m typing into.

• I would love to have Swiftkey on iOS!

• I dropped Swiftkey when I got ICS, never lookin back now that I have JB

• Does this fix the issue when backspacing in Google Chrome?

  • God, i hope so. It is really annoying.

    • Nope, still doing it when I backspace in google search

      • Damnit so much…

  • is this an issue across the board? I honestly thought i was the only one that had it, and that it was an issue with Swype.. I still don’t get the hype behind swiftkey. My buddy dropped Swype for it, and i don’t get why..

    • I’ve experienced this behavior with all 3rd party keyboards when using Chrome and only Chrome. I never use the stock browser and rarely use Aurora (new Mozilla browser) so I can’t comment on those.

    • Try it any maybe you will see, they have a trial in the play store.

• I actually prefer the Jelly Bean keyboard, I tried it a day ago and found that it did a much better job at determining what I was trying to type. It allowed me to type faster. I’ll try out this update, and see if i should switch back.

  • The stock JB keyboard is fine, but needs secondary characters on the screen. I’d rather hold down a letter for a second to get a quick number than have to press 123 , then the number, then 123 to go back to characters.

    • You can do that on stock for numbers…

  • You dont find the stock board having a bit of a lag? I like it too, but sometimes I feel that my fingers are pressing keys faster than the letters are appearing on screen….I dont condsider myself to be fast. btw, new SK upgrade is decent enough

• Hopefully one of the unnamed bug fixes is squashing what seems to be nasty memory leak that makes the keyboard unresponsive if it’s been running for over a day or so for me (on ICS).

• But JB keyboard does the trick as is!

• Light flow was too

Comments are closed.