QWERTY Keyboard: Virtual Keyboard Image Courtesy of
QWERTY Keyboard: Virtual Keyboard Image Courtesy of
A virtual keyboard is where a full-size image of a QWERTY keyboard is projected onto any surface. Touching
the image of a key generates a unique electronic signal corresponding to a key’s image. Using a
virtual keyboard eliminates the chance of breakage and infection transfer. Additionally virtual keyboards
require no cleaning and they have no wires, buttons, or switches. Virtual keyboards are also compatible with
many Smartphones and PDAs. A virtual keyboard is also called a projection keyboard. VKEY is the
trademarked name of the virtual keyboard developed by Virtual Devices Inc.
* Virtual keyboard image courtesy of Virtual Devices Inc.
INTRODUCTION
In one technology, the keyboard is projected optically on a flat surface and, as the
user touches the image of a key, the optical device detects the stroke and sends it to
the computer. In another technology, the keyboard is projected on an area and
selected keys are transmitted as wireless signals using the short-
range Bluetooth technology. Theoretically, with either approach, the keyboard
could even be projected in space and the user could type by moving fingers
through the air.
Virtual keyboard
Types[edit]
Mobile devices[edit]
Historical development[edit]
PDA[edit]
The four main approaches to enter text into a PDA were: virtual keyboards
operated by a stylus, external USB keyboards, handwritten keyboards, and stroke
recognition. Many early PDAs were not primarily focused on virtual keyboards.
Microsoft's mobile operating system approach was to simulate a complete
functional keyboard, which resulted in a slightly overloaded keyboard layout.
[11]
The main problem that early PDAs faced was support for multi-touch
technology, and as a result, usability problems for the user.
First iPhone[edit]
Android[edit]
iOS[edit]
Apple also provides the possibility for the community to develop custom
keyboards, but does not give any access to the dictionary or general keyboard
settings. Further iOS is automatically switching between system and custom
keyboards, if the user enters text into the text input field.[17][18]
The Android platform offers a spelling checker framework that offers the
possibility to implement and access spell checking in the application itself. The
framework is one of the Text Service APIs offered by the Android platform. Based
on provided text, the session object returns spelling suggestions generated by the
spelling checker.[20][21]
iOS is using the class UITextChecker, an object used to check a string (usually the
text of a document) for misspelled words, commonly known as Apple's
autocorrection. UITextChecker spell-checks are using a lexicon for a given
language. It can be told to ignore specific words when spell-checking a particular
document and it can learn new words, which adds those words to the lexicon.[22]
Word suggestions[edit]
Diverse scientific papers at the beginning of the 2000s showed even before the
invention of smart phones, that predicting words, based on what the user is typing,
is very helpful to increase the typing speed.[23][24] At the beginning of development
of this keyboard feature, prediction was mainly based on static
dictionaries. Google implemented the predicting method in 2013 in Android 4.4.
This development was mainly driven by third party keyboard providers, such
as SwiftKey and Swype.[25] Both provide powerful word search engine with
corresponding databases.[26] In 2014 Apple presented iOS 8[27] which includes a
new predictive typing feature called QuickType, which displays word predictions
above the keyboard as the user types.
Gesture typing[edit]
Haptic feedback[edit]
Haptic feedback provides for tactile confirmation that a key has been successfully
triggered i.e. the user hears and feels a "click" as a key is pressed.
Utilising hysteresis, the feel of a physical key can be emulated to an even greater
degree. In this case, there is an initial "click" that is heard and felt as the virtual key
is pressed down, but then as finger pressure is reduced once the key is triggered,
there is a further "unclick" sound and sensation as if a physical key is respringing
back to its original unclicked state. This behaviour is explained in Aleks Oniszczak
& Scott Mackenzie's 2004 paper "A Comparison of Two Input Methods for
Keypads on Mobile Devices" which first introduced haptic feedback with
hysteresis on a virtual keyboard.[29]
Another approach was researched by the Korean KJIST U-VR Lab in 2003. Their
suggestion was to use wearables to track the finger motion to replace a physical
keyboards with virtual ones. They also tried to give an audiovisual feedback to the
user, when a key got hit. The basic idea was to give the user a more natural way to
enter text, based on what he is used to.[32]
The challenges, as in augmented reality, is to give the user the possibility to enter
text in a completely virtual environment. One big issue is that most augmented
reality systems on the market are not tracking the hands of the user. So many
available system provide the possibility to point at letters.[33]
Security considerations[edit]
Virtual keyboards may be used in some cases to reduce the risk of keystroke
logging.[38] For example, Westpac’s online banking service uses a virtual keyboard
for the password entry, as does TreasuryDirect (see picture). It is more difficult
for malware to monitor the display and mouse to obtain the data entered via the
virtual keyboard, than it is to monitor real keystrokes. However it is possible, for
example by recording screenshots at regular intervals or upon each mouse click.[39]
[40]
The use of an on-screen keyboard on which the user "types" with mouse clicks can
increase the risk of password disclosure by shoulder surfing, because:
An observer can typically watch the screen more easily (and less
suspiciously) than the keyboard, and see which characters the mouse moves to.
Some implementations of the on-screen keyboard may give visual feedback
of the "key" clicked, e.g. by changing its colour briefly. This makes it much
easier for an observer to read the data from the screen. In the worst case, the
implementation may leave the focus on the most recently clicked "key" until
the next virtual key is clicked, thus allowing the observer time to read each
character even after the mouse starts moving to the next character.
A user may not be able to "point and click" as fast as they could type on a
keyboard, thus making it easier for the observer.
REFERENCES