Yesterday I experienced a little bit with the Android software keyboard, that is, the on-screen keyboard with QWERTYUIOP... keys, used by touching the keys.
However, a soft keyboard has one major difference from a physical keyboard. It is that the physical keyboard has a physical touch feeling so that it is easier to accurately locate the keys and the chance of mis-touching is much lower than the soft keyboard.
When the user touches a key in the software keyboard, there is a detected central position of the touch. That position may or may not be in the center of the keys. We can utilize this data to improve the experience of the software keyboard.
I have two ideas that may help to improve it (for now just ideas, no implementation planned anyway):
1. When the user touches the keys, after touching, display a highlight on the key touched (already implemented in the Android phone I played with yesterday), but the highlitght should be biased by the central position of the touch. This way the user can be aware that sometimes his/her touch is not in the center of the key so the next a few touches he/she can adjust the position to be nearer to the center of the key. Because the distances between the keys are fixed, it should be natural that adjustment for one key can affect another key.
2. Or, we can adjust the keyboard, move the keyboard dynamically to accomodate the average center recent of key touches.
Just something in my mind this morning. Enjoy. :)
However, a soft keyboard has one major difference from a physical keyboard. It is that the physical keyboard has a physical touch feeling so that it is easier to accurately locate the keys and the chance of mis-touching is much lower than the soft keyboard.
When the user touches a key in the software keyboard, there is a detected central position of the touch. That position may or may not be in the center of the keys. We can utilize this data to improve the experience of the software keyboard.
I have two ideas that may help to improve it (for now just ideas, no implementation planned anyway):
1. When the user touches the keys, after touching, display a highlight on the key touched (already implemented in the Android phone I played with yesterday), but the highlitght should be biased by the central position of the touch. This way the user can be aware that sometimes his/her touch is not in the center of the key so the next a few touches he/she can adjust the position to be nearer to the center of the key. Because the distances between the keys are fixed, it should be natural that adjustment for one key can affect another key.
2. Or, we can adjust the keyboard, move the keyboard dynamically to accomodate the average center recent of key touches.
Just something in my mind this morning. Enjoy. :)