Small Set Single Selector

Example of the Small Set Single Selector UX pattern.

Problem

You need to make it clear to users that only one selection is to be made from a set of choices.

Solution

Present all choices together at once, using a selection control that allows only one item to be selected.

Context

  • The number of possible choices is small enough to fit on the screen, etc that you expect users to be using.
  • Only one selection is to be made from the set of choices.

Rationale

If only one selection is to be made from a set of choices, then all you really need to be concerned with is showing all possible choices to the user, and making sure that the selection control only allows one selection.

This makes the most sense for smaller sets of items, and items that are clearly mutually exclusive. For example, it is clear to users when choosing a selection for their age range that it makes sense to choose only one selection. But in cases where multiple selections would make sense (to the user), even though you expect one selection, users may not understand why only one choice is allowed. This pattern is still appropriate in these cases, but you will want to take extra care in making it clear that only one choice is to be made, either through explanation or through the use of easy to understand selection controls.

Implementation

In most cases, you will simply want to create a list of the possible choices, with a selection control next to each item. You want to make it as clear as possible which selection control is associated with which choice. For example, if you have multiple rows and columns of items, it can sometimes be difficult to tell if the selection control on right or left of an item is the correct one to click on. Your primary goal is to make it clear to the user which item is being selected. When possible start with a vertical list of items, only moving to rows and columns when absolutely necessary because of this issue with determining which item you are selecting when multiple items are laid out horizontally. The example below shows choices laid out horizontally; notice how it might be difficult to understand quickly which selection to mark if you want to choose “Four.”Example of the Small Set Single Selector UX pattern.

Be sure to clearly mark the selected item immediately upon selection by the user.

When appropriate, provide a “none” or “other” item so that users will not be forced to make a selection even when none of the options make sense.

Help Me Get There

Infragistics has some tools that can jumpstart your efforts to implement this pattern. Broken down by technology, they are as follows.

ASP.NET

Small Set Single Selector pattern is implemented in the following ASP.NET controls: WebDataGrid, WebGrid, WebDataTree, WebDataMenu,WebListBar, WebDropDown. Check out the samples browser to see it in action.

Windows Forms

You can use the NetAdvantage for Windows Forms controls: WinGrid, WinCombo, WinListView, WinComboEditor, WinCheckEditor, WinButton, and WinOptionsSet to implement this pattern.

WPF

You can implement this pattern using the NetAdvantage for WPF controls: XamComboEditor and XamCheckEditor.

 

Examples

The primary example is taken from Internet Explorer which uses this pattern for cases where selections are mutually exclusive.

http://quince.infragistics.com/11gu

Example of the Small Set Single Selector UX Pattern Example of the Small Set Single Selector UX Pattern

Drop down lists can be used to save space and are best for shorter lists. Only the currently selected value is shown before clicking on the list, but once clicked, the list of values drops down and a new item may be selected.

http://quince.infragistics.com/1182

Example of the Small Set Single Selector UX Pattern Example of the Small Set Single Selector UX Pattern

Radio buttons are better than drop down lists because they make all options permanently visible so that users can easily consider them. They are also easier to operate for users who have difficulty making precise mouse movements. Additionally, the labels can be wider than in drop down lists (wide drop down lists don’t look good), so they can be more informative.

http://quince.infragistics.com/115p

Example of the Small Set Single Selector UX Pattern Example of the Small Set Single Selector UX Pattern

A ListBox can be used to show many choices at once, providing a scrollbar for larger numbers of items.

http://quince.infragistics.com/1110

Example of the Small Set Single Selector UX Pattern Example of the Small Set Single Selector UX Pattern

Let users select an option by clicking on either the button/box itself or its label: a bigger target is faster to click according to Fitts's Law. ASP.NET RadioButtonList controls does it by default, but with the standard HTML controls you need to code each label with a <label> element.

http://quince.infragistics.com/114l

Example of the Small Set Single Selector UX Pattern Example of the Small Set Single Selector UX Pattern

As seen in this example, icons can be used as selection items themselves. This type of use of the pattern makes sense when the selection is mapped to an action; e.g., this example is taken from a word processing application and represents choices for how to format text.

http://quince.infragistics.com/11gy

Example of the Small Set Single Selector UX Pattern Example of the Small Set Single Selector UX Pattern

Checkboxes are useful when there is only one item or a binary choice to make, and what is being selected is whether or not to enable that item.

http://quince.infragistics.com/11d7

Example of the Small Set Single Selector UX Pattern Example of the Small Set Single Selector UX Pattern

Sources

Jakob Nielsen, Checkboxes vs. Radio Buttons

Jennifer Tidwell, Designing Interfaces

Tags

Data Entry, Form.