New Android News

  • Become a Fan!

Dynamic Keyboard uses prediction to increase key size as you type

Posted In News - By AndroidPress on Monday, September 9th, 2013 With No Comments »

Third party keyboard alternatives for Android is a booming business. From Swype, SwiftKey, Fleksy and more. Today though we’ve just been tipped off about an awesome looking new app called Dynamic Keyboard. And it’s exactly that. A Dynamic keyboard that uses a powerful prediction engine like most, but the keys will actually get bigger and easier to hit as you type, and as it learns.

Screen Shot 2013-09-09 at 11.49.20 AM

Developers are constantly trying to figure out ways to allow for taster typing and text input. Swype was extremely popular back in the day, and SwiftKey brought personalization like never before. Personally I’m still stuck on Google’s Keyboard, but this new dynamic option looks pretty darn awesome.

SwiftKey has one of the best suggestion and prediction engines around, and knows what you’re about to type. While you can hit entire words to type faster, sometimes they aren’t what you want. Dynamic Keyboard (shown below) is taking a different approach. It doesn’t suggest entire words, instead of uses the prediction engine to dynamically change as you type. The next few keys in any given prediction will actually increase in size, making them easier to hit. This should help us type faster and make fewer mistakes. Check out their neat video below.

Instead of the prediction engine taking over your typing experience (which is one of my issues with it) this keyboard simply aids the user in typing more accurately. I love the idea, but hopefully that UI and all those keyboard animations can be toned down.

We’re hearing it will have tons of options, customizations, and even themes when it launches for Android on September 14th. We’ll be taking a look so stay tuned. Looks interesting right?

VIA: AndroidPolice

Leave a comment

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

Your Content Goes Here