Typing on tablets and smartphones is inconvenient. Not only because of missing tactile feedback, but also because of its size, taking such a precious real estate of your screen, because of tiny letters in small form factor devices, because of required visual feedback and because it is hard is to blind-type. Long story short, I tried to come up with something that would solve those problems.
I took several characteristics to work on:
- Ergonomic Domain
- Memory Domain
- Form factor adjustments
- Visual-motoric latency
- Precision sensitivity
- Error avoidance and correction
Letter appearance frequency (Eng):
…and came up with a “Distributed Typing” concept
When standard keyboards take half a screen, got far and static keys, does not leverage the fact that “there is no spoon” any more (physical keyboard)…
Distributed Keyboard is enabled on typing, but except for rising keyboard nothing is happening, unless you put finger or several fingers anywhere on the screen. once you put finger(s), a set of letters appear around the spot and all that is required to type it is to “slide” towards the direction (not essentially far).
It might look something like:
Fast double type anywhere is disabling the typing mode.
Texting becomes now more like sliding movement, very native for fingers without need to move the whole arm or even palm.
Letters are arranged according to appearance frequency – from more frequent, assigned to a single finger to less frequent assigned to 4 fingers (here – based on directions e.g. “ur” means “up-right” direction):
Notice that there is distinction between right and left sides of the screen for different inputs.
In small smartphone screens the typing is mostly single-handed or more correctly “single-thumb-based”, so approach here has to be a bit different.
When standard keyboard solution is like this:
I would propose more dynamic approach. Did not came up with good solution yet… For example this one is already dynamic, releasing a screen real-estate, but requires visual feedback and has long visual-motoric latency:
…So if you have a good idea on that direction, feel free to suggest )))