Keyboard

Group Members

• Alejandro Dos Reis
• Jason Strauss
• Meelap Shah
• TA: Juho Kim (juhokim@mit.edu)

Problem Statement

Many devices require text input even when a standard typing device (like a qwerty keyboard) is not available to the user.

  Examples:

• AppleTV, NetFlix with a TV remote as the interaction device
• Game consoles like XBox with a game controller as the interaction device

These devices usually present a rectangular grid of letters arranged alphabetically that the user must navigate using arrow keys (like the channel/volume controls on a tv remote) or a joystick (like on a game controller). From our own empirical evidence, typing in this way is unacceptably slow. There are several reasons why this might be:

1. The characters are arranged alphabetically in a rectangle - this greatly differs from qwerty keyboards which are by far the most common device used for typing - so the user needs to learn where letters are in these rectangles and cannot take advantage of his familiarity with qwerty keyboards. Moreover, the dimensions of these rectangles varies across devices which exacerbates the learning problem.
2. The feedback time on these devices is perceptibly longer than the familiar qwerty keyboard. The user needs to learn how long to wait after pressing an arrow button or moving the joystick before he can expect to see his selection on the screen change.
3. Navigating all 26 letters by only having one point of selection and only being able to move up/down/left/right one unit at a time unsurprisingly feels slow when we are used to 8 points of selection (8 fingers).

We would like to design a new on-screen interface for typing that allows users to type quickly when all they have is a TV remote control or game controller.

Keyboard - GR1 Analysis

Keyboard - GR2 Designs

Keyboard - GR3 Paper Prototyping

Keyboard - GR4 Computer Prototype

Keyboard - GR5 Implementation

Keyboard - GR6 User Testing