Differences between revisions 2 and 27 (spanning 25 versions)
Revision 2 as of 2011-03-29 00:39:05
Size: 1526
Editor: shoobe01
Comment:
Revision 27 as of 2011-05-15 10:30:46
Size: 6312
Editor: eberkman
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Button behaviors (look clicked, press-and hold), also select-lists, etc. - Consider them systematically to be an input selection method. So they go here! *** These are not widgets why? Because they are tied directly to the input method. A spinner is not used on a pure scroll-and-select device, because it's solving the input problem of touch only. Right??? NEED BETTER NAME!!!! == The Wheels on the Bus Go Round and Round ==
Growing up as a kid, I remember singing the song “Wheels on the Bus Go Round” on those long bus rides up to summer camp. It was the adults’ secret weapon to pass the time and keep the kids out of trouble, I presume. It went something like this:

  . The wheels on the bus go round and round,
  . round and round,
  . round and round.
  . The wheels on the bus go round and round,
  . all through the town.

  . The baby on the bus says "Wah, wah, wah;
  . Wah, wah, wah;
  . Wah, wah, wah".
  . The baby on the bus says "Wah, wah, wah",
  . all through the town...

Well, the rest of the song is outside the scope of this book. But imagine if the song was describing today’s city bus commute instead. It might go something like this:

  . The wheels on the bus go round and round,
  . round and round,
  . round and round.
  . The wheels on the bus go round and round,
  . all through the town.

  . The teen texters on the bus tap "LOL, LOL, LOL;
  . LOL, LOL, LOL;
  . LOL, LOL, LOL."
  . The teen texters on the bus tap "LOL, LOL LOL,"
  . all through the town.

  . The businessmen emails go "Clicky, click, click;
  . Clicky, click, click;
  . Clicky, click, click."
  . The businessmen emails go "Clicky, click, click;
  . all through the town.

  . The traders on the bus type "Buy, buy, buy;
  . Buy, buy, buy;
  . Buy, buy, buy."
  . The traders on the bus type "Buy, buy, buy;
  . all through the town.
Line 4: Line 43:
Forms as a way to collect information in an ordered manner pre-date computing by at least a century. Many standards were developed in the paper form era, and have translated to computerized database forms, and then to web forms. The ubiquity of the web -- to software developers if not all users -- means forms for all computing types have settled on these standard input methods. == Mobile Trends Today ==
The landscape of mobile use is defined by user-generated input. Luke Wroblewski wrote a blog post titled Data Monday: Input Matters on Mobile, and points out the following:

“Web forms make or break the most crucial online interactions: checkout (commerce), communication & registration (social), data input (productivity), and any task requiring information entry. These activities are taking off in a big way on mobile. So getting input on mobile devices matters more each day.”

So as Luke W points out, filling out fields and forms make up a large part of our mobile experience. Which is why it’s essential for UX designers to make the interfaces capable of handling the way users input and submit information.

== Slow Down Teen Texters! ==
Take a moment and reflect on some of your most aggravating moments filling out fields or entire forms on a mobile device.
Here is a common scenario that frustrates me.

First off, I’m not a savvy texter. I’m amazed by the accuracy and rate at which some people, mainly teens I’ve seen, can whip up a textual conversation at a supernatural rate. I’m embarrassed to text whenever I’m next to them. Though when I am forced to input text and characters in a field, such as an SMS, it’s very likely I’m going to make errors.

I constantly enter the wrong character because my fingers extend past the target size. Positioning the cursor to edit my mistakes is even more maddening. I end up clearing the wrong part of the word, or deleting everything I didn’t want to.
The only reason why I continue with these tasks, despite my build-up of dissatisfaction, is because, many times, there isn’t a better UI offered.

If these basic functions of inputting data fail due to an unusable interface, the user will likely not bother with the site or service. That’s a huge risk, considering the emerging trends users are engaged in with their mobile device.
Line 7: Line 62:
== Input and Selection in the Mobile Space ==
This chapter will explain input and selection patterns that can be used to maintain a usable interface. Here are some general guidelines to consider:
Line 8: Line 65:
WEBFORM SUMMARY:
text – a simple text box that allows input of a single line of text (an alternative, password, is used for security purposes, in which the characters typed in are invisible or replaced by symbols such as *)
checkbox – a check box
radio – a radio button
file – a file select control for uploading a file
reset – a reset button that, when activated, tells the browser to restore the values to their initial values.
submit – a button that tells the browser to take action on the form (typically to send it to a server)
textarea – much like the text input field except a textarea allows for multiple rows of data to be shown and entered
select – a drop-down list that displays a list of items a user can select from
=== Use functions that promote quick and efficient input ===
 * Consider using assistive technology such as autocomplete and prediction during text entry.
 * Limit the amount of unnecessary "pogo sticking" and selecting of key controls. For example, when you begin entering an email address, consider the benefit of having a key labeled as ".com" predicatively appear to save the user from typing those additional four characters.
 * Consider the principles of Fitts Law. The more clicks it takes to make a selection, the longer it takes as well. Therefore, use appropriate controls to limit the amount of steps a user has to make to get a desired result.
 * Don’t remove your users from context when an input of data is required. Keep input selections on the same page.
 * Text fields may not be the most effective choice. They result in many user errors. Carefully consider context of use and user needs. Maybe a dropdown list may be more effective and efficient.

=== Use vertical space effectively ===
 * On small display devices, titles should be placed above the input area field. This will save vertical space. Do not place titles to the left or right, this will reduce the size of the input field or will require horizontal scrolling.
 * When using labels, having them placed inside the field can save space. If that’s not an option, use short labels to the left of the field.

=== Provide clear affordances ===
 * When information occurs within a circular range, provide visual cues that the range will loop back to its initial value. Spinners can accomplish this.
 * Use tape controls to indicate a linear range of value. Values are restricted within that length of tape and are not to exceed beyond the scale. Use labels to indicate range.
 * Length and size of the text field is a clear indicator of its capacity.

== Patterns for Input & Selection ==
Using Input & Selection functions appropriately provides users methods to enter text and make selections within a list or field. Within this chapter, the following patterns will be discussed.

[[Input Areas]] -- Provides a method for users to enter text and other character-based information without restriction.

[[Form Selections]] -- A method is provided for users to easily make single or multiple selections from pre-loaded lists of options.

[[Spinners & Tapes]] -- A simple, space-efficient method must be provided for users to easily make changes to a setting level or value.

[[Clear Entry]] -- Users must be able to remove contents from fields, or entire forms, without undue effort and with a low risk of accidental activation.

The Wheels on the Bus Go Round and Round

Growing up as a kid, I remember singing the song “Wheels on the Bus Go Round” on those long bus rides up to summer camp. It was the adults’ secret weapon to pass the time and keep the kids out of trouble, I presume. It went something like this:

  • The wheels on the bus go round and round,
  • round and round,
  • round and round.
  • The wheels on the bus go round and round,
  • all through the town.
  • The baby on the bus says "Wah, wah, wah;
  • Wah, wah, wah;
  • Wah, wah, wah".
  • The baby on the bus says "Wah, wah, wah",
  • all through the town...

Well, the rest of the song is outside the scope of this book. But imagine if the song was describing today’s city bus commute instead. It might go something like this:

  • The wheels on the bus go round and round,
  • round and round,
  • round and round.
  • The wheels on the bus go round and round,
  • all through the town.
  • The teen texters on the bus tap "LOL, LOL, LOL;
  • LOL, LOL, LOL;
  • LOL, LOL, LOL."
  • The teen texters on the bus tap "LOL, LOL LOL,"
  • all through the town.
  • The businessmen emails go "Clicky, click, click;
  • Clicky, click, click;
  • Clicky, click, click."
  • The businessmen emails go "Clicky, click, click;
  • all through the town.
  • The traders on the bus type "Buy, buy, buy;
  • Buy, buy, buy;
  • Buy, buy, buy."
  • The traders on the bus type "Buy, buy, buy;
  • all through the town.

The landscape of mobile use is defined by user-generated input. Luke Wroblewski wrote a blog post titled Data Monday: Input Matters on Mobile, and points out the following:

“Web forms make or break the most crucial online interactions: checkout (commerce), communication & registration (social), data input (productivity), and any task requiring information entry. These activities are taking off in a big way on mobile. So getting input on mobile devices matters more each day.”

So as Luke W points out, filling out fields and forms make up a large part of our mobile experience. Which is why it’s essential for UX designers to make the interfaces capable of handling the way users input and submit information.

Slow Down Teen Texters!

Take a moment and reflect on some of your most aggravating moments filling out fields or entire forms on a mobile device. Here is a common scenario that frustrates me.

First off, I’m not a savvy texter. I’m amazed by the accuracy and rate at which some people, mainly teens I’ve seen, can whip up a textual conversation at a supernatural rate. I’m embarrassed to text whenever I’m next to them. Though when I am forced to input text and characters in a field, such as an SMS, it’s very likely I’m going to make errors.

I constantly enter the wrong character because my fingers extend past the target size. Positioning the cursor to edit my mistakes is even more maddening. I end up clearing the wrong part of the word, or deleting everything I didn’t want to. The only reason why I continue with these tasks, despite my build-up of dissatisfaction, is because, many times, there isn’t a better UI offered.

If these basic functions of inputting data fail due to an unusable interface, the user will likely not bother with the site or service. That’s a huge risk, considering the emerging trends users are engaged in with their mobile device.

Input and Selection in the Mobile Space

This chapter will explain input and selection patterns that can be used to maintain a usable interface. Here are some general guidelines to consider:

Use functions that promote quick and efficient input

  • Consider using assistive technology such as autocomplete and prediction during text entry.
  • Limit the amount of unnecessary "pogo sticking" and selecting of key controls. For example, when you begin entering an email address, consider the benefit of having a key labeled as ".com" predicatively appear to save the user from typing those additional four characters.
  • Consider the principles of Fitts Law. The more clicks it takes to make a selection, the longer it takes as well. Therefore, use appropriate controls to limit the amount of steps a user has to make to get a desired result.
  • Don’t remove your users from context when an input of data is required. Keep input selections on the same page.
  • Text fields may not be the most effective choice. They result in many user errors. Carefully consider context of use and user needs. Maybe a dropdown list may be more effective and efficient.

Use vertical space effectively

  • On small display devices, titles should be placed above the input area field. This will save vertical space. Do not place titles to the left or right, this will reduce the size of the input field or will require horizontal scrolling.
  • When using labels, having them placed inside the field can save space. If that’s not an option, use short labels to the left of the field.

Provide clear affordances

  • When information occurs within a circular range, provide visual cues that the range will loop back to its initial value. Spinners can accomplish this.
  • Use tape controls to indicate a linear range of value. Values are restricted within that length of tape and are not to exceed beyond the scale. Use labels to indicate range.
  • Length and size of the text field is a clear indicator of its capacity.

Patterns for Input & Selection

Using Input & Selection functions appropriately provides users methods to enter text and make selections within a list or field. Within this chapter, the following patterns will be discussed.

Input Areas -- Provides a method for users to enter text and other character-based information without restriction.

Form Selections -- A method is provided for users to easily make single or multiple selections from pre-loaded lists of options.

Spinners & Tapes -- A simple, space-efficient method must be provided for users to easily make changes to a setting level or value.

Clear Entry -- Users must be able to remove contents from fields, or entire forms, without undue effort and with a low risk of accidental activation.

Input and Selection (last edited 2011-12-13 19:21:22 by shoobe01)