Testing Swiftkey for iOS 8by Brandon Chester on September 16, 2014 9:00 PM EST
- Posted in
- iOS 8
Earlier this week SwiftKey announced that they hope to have their keyboard available on the App Store when iOS 8 finally rolls out to users worldwide. They've been kind enough to provide us with a beta version of the SwiftKey keyboard for testing, along with some insight into developing extensions on iOS 8 and their hopes for SwiftKey's future on both iOS and Android.
Assuming that nothing delays Apple's approval for the app, the first step for users who want to get SwiftKey after upgrading to iOS 8 will be to download it from the App Store. Due to the nature of Apple's implementation of extensions, even applications on iOS 8 that are essentially just extensions meant to run in other apps must have a container application that gets placed on the home screen. In the case of SwiftKey this is fine, as the application is home to settings for SwiftKey Cloud, languages, settings, and themes.
Once you've installed SwiftKey from the App Store, you'll need to go into the settings app to add it as shown in the image above. With the app installed the SwiftKey keyboard would show up in the section to add a new keyboard under a header for third party keyboards. Once you've done this you'll be ready to start using SwiftKey. However, you may notice that there's one very important thing missing.
Swiftkey immediately after installation on an iPad
As you can see above, the bar for predictions is covered by a banner asking the user to enable "full access." This is because of the sandboxing that Apple does for third party keyboards on iOS. Third party keyboards are, by default, placed in an extremely restrictive sandbox. They are unable to get information about what words are being inputted or what content is in an app, and they are unable to access networking to do server side prediction. These measures are in place to protect the user's privacy and security. To enable extended functionality, Apple allows users to enable full access for third party keyboards in the settings app. By doing this, SwiftKey is able to grab what characters are being typed to use with their prediction and correction technology which learns more about how a user types and what mistakes they make.
As far as the design of the keyboard goes, its layout is essentially same as the stock iOS keyboard so there's no real learning curve. Users who are familiar with the iOS keyboard can start using SwiftKey and feel at home right off the bat. iPad users will notice that the keys are larger than the stock keyboard, which in my experience made keys easier to hit without causing me to hit the wrong key due to the reduced amount of space between them. In addition to its accuracy, it's also extremely responsive. iOS 8 on the third generation iPad I was using for testing has an enormous delay between when you touch a key and when it actually registers. SwiftKey has no such issue, and for that reason alone it has become my daily keyboard on iPad. As for its appearance, the keyboard currently only comes with the nickel dark and nickel light themes that you see above.
Swiftkey's application, much like the keyboard itself, fits in very well with the visual style and design conventions of iOS. It's obvious that some care has been put into making it more than a port of the Android version of SwiftKey. The application is home to all the settings for the keyboard, including themes, languages, and SwiftKey Cloud. Currently not all the settings from the Android version have been brought over. Layout options and themes are two notable omissions. However, this is a first release, and I've been told that there will definitely be updates as time goes on.
With iOS including Apple's QuickType keyboard with similar correction and suggestion functionality, some users may be wondering why they even need a third party keyboard like SwiftKey. For me the most obvious reason is SwiftKey Cloud. My current setup is an HTC One (M7) and an iPad. Using SwiftKey on my phone but the stock iOS keyboard on the iPad would mean that the information each keyboard learns about how I type would not available to both keyboards. With SwiftKey on iOS and SwiftKey Cloud, all the information Swiftkey has collected about how I type and what mistakes I often make are available to both of my devices. This is a huge advantage for people who have mobile devices running multiple operating systems.
Another advantage that can be argued is that SwiftKey is a company that has had their keyboard available for 4 years, and specializes only in keyboards. It's not unreasonable to think that SwiftKey's technology for learning from how the user types may be more mature than Apple's which is just now being introduced with iOS 8.
The last advantage simply comes down to features. SwiftKey, and other third party keyboards, can always offer more features than Apple does due to their focus only on keyboards and the ability to ship updates whenever necessary via the App Store. One notable feature that SwiftKey offers is Flow, which is a method of typing by moving your finger from key to key. Users who use Swype by Nuance will be familiar with how SwiftKey Flow works. Unfortunately, I was unable to test Flow as the iPad version of the keyboard does not have it. This is due to memory limitations imposed on extensions. The functionality and visual effects for SwiftKey Flow when run on an iPad exceeds this amount of RAM which is why only the version for iPhone and iPod Touch includes it. Flow is most useful in a one handed situation on a phone so I'm not heartbroken by its omission in the iPad version. That being said, I am still hopeful that SwiftKey will be able to do further optimization to eventually bring Flow to iPad.
Overall, I'm very happy with how SwiftKey has turned out on iOS 8. The SwiftKey Note application makes it clear that the company has wanted to bring their keyboard to iOS for some time now and has just been blocked by the lack of third party keyboard support. The fact that it fixes the keyboard lag on my iPad and syncronizes what it has learned across iOS and Android are enough to make me very happy to use SwiftKey on iOS. I'm very excited to see what future updates bring.
SwiftKey should be available for free on the App Store not long after the release of iOS 8. The application is subject to Apple's approval, and so there could be some delay in its availability to users.
Update: SwiftKey is approved and available on the App Store now. Grab it here.
Post Your CommentPlease log in or sign up to comment.
View All Comments
jjj - Tuesday, September 16, 2014 - linkDon't think you guys have ever tested an Android app but this is the second iOS app (after Bioshock) in less than a month.
RagnarKon - Tuesday, September 16, 2014 - linkAlright gotta call this one out.
I don't like Apple anymore than the next person... but out of the 30+ articles Anandtech has published on smartphones in the past month, only five of them have been about Apple.
Only five articles total... during the month Apple announced their new phones. I know you gotta keep your Apple hate level high to make it possible to sleep at night... but gotta be rational about it.
krutou - Tuesday, September 16, 2014 - link7 of 33 "Smartphone" tagged articles have been about Apple products or related features: 1. SwitfKey First Look, 2. SwiftKey Announce, 3. Dual Domain Pixels, 4. Hands on iPhone 6/6+, 5. Announce iPhone 6/6+, 6. Bioshock for iOS, 7. A month with the iPhone 5S.
Of the remainder, 6 are platform agnostic: 1. USB Type C, 2. TMobile Uncarrier 7.0, 3. Nvidia Patent Lawsuit, 4. Broadcom BCM4358, 5. Intel XMM6255, 6. State of the Art SoC.
Compare that to 17 Android (4 Samsung), and 3 Windows Phone.
Considering Samsung controls double the marketshare Apple does, and equivalent revenue, Samsung should have equivalent or more articles than Apple.
batongxue - Tuesday, September 16, 2014 - linkSpeaking of high level of Apple hate, you amazed me.
althaz - Tuesday, September 16, 2014 - linkExcept that LOTS of Samsung stuff is covered in general Android articles (and the stuff that's not is generally Samsung making their phones worse by not sticking to the normal Android implementation of things).
There has been a fair bit of Apple stuff lately, it's not like Anandtech is turning into Applewatch.com or something (I have no idea if that's a real website).
Mayuyu - Tuesday, September 16, 2014 - linkYeah but there's nothing to write about android devices. How many times can you read about another generic android device with a snapdragon soc?
eanazag - Wednesday, September 17, 2014 - linkExactly, there isn't that much that has changed.
Spunjji - Wednesday, September 17, 2014 - linkMore times than you can read about a set of devices from the same manufacturer with the same OS and the same SOC designer... seriously, I don't entirely agree with the anti-Apple whining here but there's no logic to your statement.
solipsism - Wednesday, September 17, 2014 - link1) If you're going to say something is platform agnostic because it could be added, like USB Type C, but won't, then Swiftkey falls under that. These animate gif demos work the same on Android.
2) Samsung controls more marketshare from crap devices which is like expecting food critics to only write about McDonalds due to the number of meals they sell. Even most of their smartphones should really be classified as feature phones. Sure, they make some high-end devices but they don't sell nearly as many as Apple will. Do you really want a 10 page review on every shitty sub-$100 device that Samsung makes? Of course you don't so stop complaining. AT does excellent reviews on the Samsung devices that matter to their readers
3) If you don't like reading reviews technology that may include an Apple product from time to time then don't read those fucking articles. Pretty damn simple solution.
AppleCrappleHater2 - Tuesday, September 23, 2014 - linkBecause they want to go back to waiting 2-4 years (if ever) for Apple to grudgingly get around to copying what Android delivers NOW? While it's nice that you're doing volunteer work at the mental hospitals, people in straitjackets aren't really a reliable cadre to make predictions with.
Widgets that you have to look at the notification screen (something else Apple copied) to check? Finally having a third-party keyboard like SwiftKey which I've used since 2010 on my Android devices? Wow. So progress. Much copy. Apple has sorta copied (in their typical half-arsed manner) a few of the things Android has done for years and now iOS mavens will lemming charge back home because the iPhone Galaxy and Galaxy Note have screens the same size as what they've had for years already? That's cuckoo nuts totes cray cray.
I picked up a cheap used iPad to see what the big deal was and "BIG DEAL!" was my reaction at the rigid, inflexible, screw-the-user-and-think-the-way-Apple-commands constraints of the OS. From a usability and aesthetic perspective, it was a great leap backward. I was honestly stunned how anyone can consider iOS to be anything but inferior in every way. (I've even had hardcore Apple fanboys reluctantly admit that my observations were correct. One whimpered, "Yeah, getting anything on or off my iPad is a chore because of the lack of a file structure.")
Add on the proprietary chargers and only fools with more dollars than sense would flock away from the openness and and advanced environment that is Android for the pale pastel pastiche which is iOS. And when Android L hits, the gap will only widen farther, but buck up lil' iChumps, perhaps iOS 11 will rip-off, I mean copy, er, adopt a few of its features.