Swiftkey just got an update that lets you swipe on the iPad. Pretty cool.
In what world is Swyping on an iPad even remotely faster than tapping keys? Seems you'd have to swype pretty damned far, almost too far that any 'speed' gained would be lost by how far you had to track? It's barely saving time on an iPhone IMO. (not trying to be smarmy)
Well, this is wacky: https://www.macrumors.com/2015/02/12/phorm-morphing-ipad-mini-keyboard/
Grow your own keyboard?
In what world is Swyping on an iPad even remotely faster than tapping keys? Seems you'd have to swype pretty damned far, almost too far that any 'speed' gained would be lost by how far you had to track? It's barely saving time on an iPhone IMO. (not trying to be smarmy)
In what world is Swyping on an iPad even remotely faster than tapping keys? Seems you'd have to swype pretty damned far, almost too far that any 'speed' gained would be lost by how far you had to track? It's barely saving time on an iPhone IMO. (not trying to be smarmy)
Finally. Something we could do all along with e.g. Swype and Path Input.
I still hope that Swype will come up with a similar iPad keyboard (numeric pad too) as Path Input has because besides the swipe gestures i sometimes want to type words and that works best with Swype.
- Next-word prediction is back
- Algorithm improvement : Stop at the "r" in "art" while swiping with one finger, and you'l be able to hint the "r". It used to hint double letters, change back to the old mode from options.
- Top-bar learning UI is revamped. You can enable the old way (instant open) from the options menu
- Press-hold an empty top part of the topbar, and shortcut slots are there for your use
- Much improved autospace mode
- Fixed capsed words issue
- Autocorrect when cursor is just at the end of the word is now disabled
- Lots of bugfixes
- Fancy new themes
- Lots of other new stuff
- Simpler options menu
Anyone else XP this common bug where the keyboard fails to appear making the user force close the app then re open it? I'm referring specifically to fleksy and swiftkey. I was just wondering if I should just wait until iOS 8.2 before using these custom keyboards again.
This bug is still present with SwiftKey even on the latest iOS version. It's frustrating as hell and makes me want to give up on custom keyboards altogether.
Anyone else using third party keyboards on the new ios 8.2? Has that damn keyboard disappearing bug been worked on?
Uninstalled what?You still get no keyboard on the lock screen and last night, I got no keyboard in iMessages when I tapped into the dialogue box to reply.
Uninstalled.
Will try again in 8.3, I guess.
Uninstalled what?