Differences between revisions 4 and 5
Revision 4 as of 2011-03-28 15:33:57
Size: 8226
Editor: shoobe01
Comment:
Revision 5 as of 2011-03-28 16:02:05
Size: 8099
Editor: shoobe01
Comment:
Deletions are marked like this. Additions are marked like this.
Line 30: Line 30:
All typed characters are always entered into the phone number field, and the matching results are in a separate space. This is a variant of '''Autocomplete & Prediction''' but never replaces the characters entered in the field until the user deliberately selects them.  **** BE MORE CLEAR AND REFER TO THE RIGHT TYPE FROM THAT PATTERN. **** All typed characters are always entered into the phone number field, and the matching results are in a separate space. This is the "suggestion" variant of the '''[[Autocomplete & Prediction]]''' pattern, which see.

Problem

Most mobile devices are still centered around voice networks connected to the PSTN. Access to a phone dialer must be provided.

Solution

Numeric entry for this dialer application or mode varies from other entry methods, and has developed common methods of operation that users are accustomed to, so must be followed to provide easy and accurate access to the voice network.

This pattern is concerned with only the numeric entry and certain aspects of the overall interaction of the Dialer application. Numerous additional features and details of the operation are not discussed here, largely for space concerns. Follow the guidelines from the operator, especially as the regard local regulatory and interoperability needs.

Variations

For most of the history of mobile devices, telephony was the key feature, and was integral to the device at all levels. This is still the method employed for almost all devices with a dedicated numeric keypad. From the Home & Idle Screens keypad entry will result in switching to the Dialer mode, and the entered character being typed onto the screen.

The Dialer application does not need to be deliberately activated as the handset is considered a phone when not otherwise engaged. Naturally, when in other applications, the keypad is used for text or numeric entry within that context, or to activate Accesskeys and does not immediately launch the Dialer.

A variation employed first by "PDA phones" and now by most smartphones is to make the Dialer just another application on the device, with few or no special UI conditions. In these cases, dialing cannot be initiated directly from the Idle screen. The Dialer application must instead be deliberately launched before any characters can be entered.

The Dialer application is very often closely coupled with -- or a part of -- address books, call history and other features. However, only the Dialer itself will be discussed here.

Interaction Details

Characters entered will appear in the phone number field, generally near the top of the viewport. Character entry is much as any other text entry, with a cursor and the ability to delete characters using the "back" or "delete" function.

Matching results will appear below this field. Matching is the practice of providing extended information about the number entered so far. A live search of the address book will be performed as characters are typed. Users may select from the list displayed, or simply confirm that the dialed entry is correct.

For example, if the characters "210" are entered, the following items (already in the address book) may be listed:

  • Jane Adams 816 210 0123
  • Dee Adler 210 618 0567

All typed characters are always entered into the phone number field, and the matching results are in a separate space. This is the "suggestion" variant of the Autocomplete & Prediction pattern, which see.

If no address book match is found, the region (e.g. U.S. state) corresponding to the number format, when available, may be displayed instead. For example, as soon as "816" is typed, with no matches, "MIssouri" may be displayed (as this area code is entirely within that U.S. state).

Errors and null-value information will not be displayed when address book or regional matching is not available or not found; simply display no matches at all.

Pressing the Talk button is generally required to dial a call or select a match from the list.

There is no significant variation for the use of a virtual, on-screen keypad. When visible, the same behaviors take place. Virtual keypads are usually presented as only one of several options, so may not be available by default when the Dialer application is open, or when a call is initiated or received. Easy and unambiguous access to the keypad must be provided at all times.

If the user presses and holds a numeric key, this will initiate a shortcut and dial the corresponding number. If no shortcut is assigned, no special action should be taken and no errors displayed. The key will simply be entered as though a short-press was performed.

The shortcut character should appear on the screen, to confirm it has been entered. These may display inside the phone number field (usually with a special character to indicate the difference, such as a preceding pound) or may be displayed in a different manner, such as a momentary overlay.

The 1 key is most often reserved for voicemail, though this may vary based on operator standards.

Whenever a call is active --- whether sent or recieved -- a version of the Dialer is generally made available in order to allow selection of extensions or entering information in IVR (interactive voice response) systems. The same principles will be followed as in the dialer, with

Presentation Details

The Dialer screen will be fixed, with elements remaining in the same location and always visible. Selectable items which must scroll (such as name matches) will do so only within a small area and will not scroll the entire page.

The number entered must display in a common, readily recognized format for the locale. In the U.S. this would mean the characters 8162100455 display as 816-210-0455, for example. Avoid wrapping the primary number to a second line; if needed due to space, break at the end of the dialed number so that extensions and IVR entries are on the second (and third...) lines.

Special functions for use while the call is active, such as mute, and speaker may be presented as on-screen buttons for touch or pen devices. Whenever possible, display these alongside virtual keypads instead of requiring switching from keypad to control mode.

Additional functions, such as 3-way calling should be placed under options menus, such a Softkeys. The exact implementation will vary depending on the OS standards of the device. Avoid hiding important and frequently used in-call features, such as mute, speakerphone and headset controls under options menus, even for scroll-and-select devices. Place on-screen whenever possible to expose the function.

Display the current state of the device when on a call. The time on call, connected status and audio features (mute, speaker, headset) should be clearly visible on the screen, without scrolling or searching inside options menus.

KEY LABELS... I FEEL I ALREADY DID THIS (EVEN NANP REFERENCE) SO NEED TO GRAB THAT FROM THE KEYBOARDS AND KEYPADS SECTION.

When the Dialer is displayed for address book entry, formatting hints or optional entry methods should be provided. Hard pause, soft pause and international dialing codes are not directly supported by the keypad, so will require special methods (such as menus or custom buttons) or informing the user of keypad shortcuts.

Antipatterns

Characters entered must be typed immediately and each character entered as typed. Do not require a "wake-up" character to open the Dialer but then be ignored, even if all subsequent characters are entered correctly.

Do not include un-necessary functions. For example, pause characters are not needed when live dialing, just when saving entered information to the address book.

Avoid hiding virtual keypads behind ambiguous labels. Whenever practical, place a "Keypad" button, with a suitable iconic label, on the screen or as a primary Softkey.

Whenever possible, increase the time that screen backlight is entirely removed, in order to allow the user to see the current state of an ongoing call without handing the device.

The OK/Enter button should not perform unexpected or out-of-domain functions. For example, when selecting a match from the list, it should either dial or display additional options. However, a default condition (or pressing the Talk key from here) should dial the call. Loading the address book would be confusing and make it difficult for the user to dial the call quickly and without error.

Examples

Dialer (last edited 2011-07-31 23:20:50 by shoobe01)