iOS8 3rd Party Keyboards Reviews - SwiftKey and Swype
I've been running iOS8 for a while now in Beta, and today all my iDevices are running the released iOS 8. One of the most anticipated new features is the ability to create and add 3rd party keyboards. In the future I anticipate we'll see lots of interesting and creative keyboards, perhaps to draw an emoji with your finger, custom Chinese or Japanese IMEs (input method editors), and others.
Until then, the primary thing folks have been waiting for is what Android and now Windows Phone have had for a while, the ability to type without lifting your thumb. You'll either love it or hate it, but you need to try it for a day. When done well, it's amazing and brilliant.
The Hassle of the Setup Process
3rd Party Keyboards install from the AppStore like any other app. When you run each for the first time they walk you through the process of installing their keyboard. This is easy for a techie, but for your non-Technical Relatives it might take a little coaching as you'll end up 3 or 4 deep inside Settings | General | Keyboards.
Swype - US$0.99
Swype worked great, exactly as advertised. I enjoyed using it very much and it's swiping feature works as advertised. I did feel its autocorrect somehow left something to be desired. Below you can see it getting confused as I swipe the word "autocorrect."
The deal breaker for me with Swype was two-fold. First, the spacebar is smaller than the default space bar. It's a small thing to be sure (as tiny keyboards are) but it had me adding periods . throughout . my text, as I hit that before I hit the space bar.
Secondly, the lower left corner of the iOS keyboard has always been the little 123 Icon. It lets you switch between ABC and 123, of course. Swype chose to move this over to the second spot. This flummoxed me all day. I'm sure I could train myself as it's just muscle memory, but it was an unusual choice, I thought, and this is just one place where Swype deviated their keyboard design from being "just a swiping solution." They've moved other things as well.
Opening the proper Swype button in the lower corner with a press and hold brings up the Globe (usually not hidden in other keyboards) as well as the Dial Pad for numbers, and the Settings gear.
Swype has moved some things and this slowed me down quite a lot. This keyboard below moves all my symbols to new locations, with the Asterisk nowhere to be found!
NOTE: One thing that ALL these keyboards thankfully fix is the "shift key problem" with the default iOS keyboard. They show lowercase letters when you're typing lowercase, and change the whole keyboard to uppercase when you press Shift. It's so painfully a problem with the default keyboard, it's really unfortunate that this wasn't changed in iOS8.
Swype also includes funky themes with background images if you're into that level of customization.
SwiftKey - Free, with registration and has optional $ IAPs
SwiftKey is free, but they intend to make money by selling us keyboard things. For now, I'm thrilled with the default, as seen below. It looks almost exactly like the default iOS keyboard, which is what I'm looking for. I don't want to relearn where things are when I just want swiping and a few other features.
SwiftKey keeps all the symbols and numbers exactly where they usually are, and adds a few nice touches like a gentle reminder than I can touch-and-hold on punctuation for additional choices.
One odd bug I saw with SwiftKey - If I turn off "Allow all Access," in Settings | General | Keyboards, SwiftKey ignored my white theme choice, showing me only a black keyboard with a reminder to turn on All Access. I presume this is a bug, as it's definitely wrong. Other than this one issue, I'm digging SwiftKey.
There is also a free Chinese keyboard called TouchPal that includes swiping input, keyboards, themes and a focus on Emoji. The Emoji are included in the keyboard, meaning your don't need to switch to the Emoji keyboard. That said, I installed it and my phone locked up. I rebooted and had no keyboard until I removed TouchPal. I think this experience speaks (IMHO) to the larger issue of stability with 3rd party keyboards on iOS, but this is only from my perspective as a user. I was unable to get TouchPal working.
Here's the kicker for a lot of people. In order to make predictive text suggestions, sometimes these keyboards need to send what you're typing to their cloud engine. Be sure to read their privacy policies to make sure you're comfortable with how they use your data.
For users that opt in to SwiftKey Cloud, we will collect your email address, basic demographic information and information concerning the words and phrases that you use (“Language Modeling Data”) to enable services such as personalization, prediction synchronization and backup. We may use data provided by you to develop and improve our Products.
Where a field has been flagged by a website or app as denoting a password field or payment information, SwiftKey does not log, store or learn from this information.
Be educated, but I'm OK with using these keyboards for basic email. Of course, you can (and will) switch keyboards many times a day if you're like me.
If you type technical (or Medical, or Legal, or whatever) things a lot, you'll likely find some very odd predications with these keyboards. Here SwiftKey has clearly looked at my history and is suggesting something totally wrong...and offering to Capitalize it also! Autocorrect has always been a problem, but don't expect a 3rd party keyboard to fix it...although these ones aim to try! Theoretically they'll learn even more from what I type.
A number of times I've found myself looking at a text box with a flashing insert point waiting for a keyboard to pop up. These keyboards need to LOAD and sometimes that causes a pause, or when things go wrong, they just never show up. In a word, there's bugs all around, in both the Keyboards, I suspect, and in iOS8's handling of them.
Here I am, keyboardless. I had to reboot at this point. Your mileage may vary.
Mark my words, I predict bug fixes for a the supporting APIs for 3rd Party Keyboards will be coming in the next minor update to iOS8.
NOTE: Neither of these keyboards includes a Microphone Button to start Siri's built-in dictation. As such, these keyboards won't work with my app, myEcho. This appears to be a limitation imposed by Apple, that won't allow us (developers) to invoke a dictation without using their button. If you want to dictate (which is almost a keyboard on its own...I'd like to see a giant "Dictate now" button, myself) then you'll need to switch to the built in iOS keyboard.
My recommendation? YOU should try them all and see which one makes you happy. If you are very much a touch typist and you want a swiping keyboard that doesn't deviate far from the default, I recommend SwiftKey.
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.
Just wondering as I did not see that written in here.
In addition to the best swiping experience, I find it hard to live without (in no particular order):
-double tap the Swype button to select the current word.
-Swype from the Swype button to x,c, and v for cut, copy, and paste. And from Swype to a for select all, and Swype to t/5 to bring up the number pad.
-Swype to shift and lets you select capitalization.
-uncanny Dragon speech recognition (again, Android only I'm guessing).
-auto spacing between words.
-delete whole word with one backspace.
There are features on SwiftKey that I wish I could bring over, and later versions seem to introduce some memory lag (especially with bigger bodies of text), but too much good stuff.
When I get a text and I open messages and Swype is the default keyboard, it's not at the most recent message and I have to scroll down to the latest message to see what the other person sent?
Swype was behaving oddly for me last night, I've not yet gotten back to more testing. But, while replying to a tweet in TweetBot on my iPad, the text output just fine, but when I sent it, my text disappeared, leaving only the recipients in the message.
Not sure if this is a TweetBot or Swype issue, but have since removed both keyboards and will give them a shot after some updates or when I have more time to play.
This has started to bug me so much that I switched back to the default keyboard. :-/
- Swype does not support Portuguese which is a dealbreaker. Also, in French it forces you to use AZERTY (used in France) and won't let you switch to QWERTY (used in Canada, for example)
- SwiftKey supports several languages _and_ dialects (French Canadian, Brazilian Portuguese) but is limited to only two active languages and changing them requires you to leave whatever app you're using.
Again, not a problem for English-speakers (or, in the case of SwiftKey, speakers of only 1 or 2 languages), but a total deal breaker for me.
All that said, the native iOS keyboard actually works well enough and the new predictive text is really good.
I'm looking forward to the switch of an existing iOS7 app called Path Input which is already available for iPad and iPhone and will soon be upgraded to iOS8 keyboard. Path Input already supports Dutch in the current app and works great!
Noticed a bug with SwiftKey while using Evernote, where the Return/Enter key in SwiftKey oddly doesn't seem to work the same as on the default keyboard.
Normally, in Evernote (iPhone), if the current line begins with a checkbox (i.e. while writing a to-do list within a text document), when you press Return on the default keyboard, a new checkbox automatically appears on the next line.
With SwiftKey, this doesn't happen, and the new checkbox needs to be added manually. Which is a hassle.
Seems like an odd bug -- how complicated can sending a "Return" keystroke to the open application be? Complicated enough, apparently.
This is also why it probably just defaults to the dark keyboard when you don't allow full access. If you set the the color scheme in the app, but don't allow full access, the keyboard has no way to retrieve it's setting from the app, since you've disallowed it. So, the dark keyboard is probably just the default case when this happens. I don't think this is a bug, more like an intentional error handling choice.
"Thank you for contacting Swype Support! We apologize for the delay in this response.
This issue is actually on Gmail's side. Swype only enters the letters and it is up to Gmail to interpret and trigger a contact suggestion bar. We have escalated it to them as it seemed that they are not compatible with the recent third party addition to the iOS.
We are also fixing things on our end to make sure issues like this will be addressed. Please keep an eye out to the App Store for the latest Swype and Gmail updates. Feel free to reach me back if you have clarifications.
Nuance Mobility Support
Comments are closed.