Well! After lots of hard work behind the scenes, we’re now very proud to reveal SwiftKey X!
Our new public beta, which is available for free on Android Market, is packed full of new features (as described on our apps page). You can download it as http://skx.me/beta – and please share this link with EVERYONE!
And the best news is that when this launches as a full app, it’ll be free for folks who have already bought SwiftKey.
Check out our press release, below:SwiftKey X Beta – This time it’s personal.
We’re looking for a full-stack web developer to join the best company in the world – TouchType – to do a variety of fun, engaging and innovative things with our technology.
Do you think you fit the bill? If so, check out our job description here. No recruiters please.
Thanks to everyone who took part in our 1,000,000 download survey. We had a phenomenal response and can confirm the winners as follows:
Quentin Campbell, from Florida, USA, who chose an Apple iPad 2 Black 64GB;
Aman Sanghvi, from India, who chose a Blackberry Playbook 64GB;
Austin Szabo, from California, USA, who chose an Apple iPad 2 Black 64GB.
Stay posted for some interesting insights from the results, coming soon!
As we saw in part 2 of this series, mocking Android’s
PowerManager service directly is impossible. But there is an alternative approach that gives us something close enough. This article describes that approach.
In part 1 of this series, I showed how to mock an interface that we created ourselves under Android. That’s useful, but mocking really pays dividends when mocking OS services—doing so allows us to test our code in isolation, verify that it interacts with the OS correctly and that it handles errors properly.
In the next few “Technical Wizardry” articles, we’re going to look at the approach we’ve developed to help with testing Android code (first published here).
Welcome to the new “Technical Wizardry” section of the TouchType blog. Here’s where we’ll be sharing a few of the tips and tricks we’ve learned while developing SwiftKey and the Fluency prediction engine that underpins it.
We’re going to start off with a series of articles on Android development (originally published here).