It isn’t easy to figure out when to use a salad fork or dinner fork just by looking at them. This difficulty is caused by the fork’s similar form and function. Both have prongs for spearing food, but each is designed for a different food course.

Similar Functions but for Different Contexts

Forks confuse people in the same way that switches and checkboxes confuse designers. Many designers think it doesn’t matter when you use one or the other. But the arbitrary use of them can cause unexpectedness and confusion. Like forks, these user interface controls are for different contexts.

Switches and checkboxes are both used to enable settings. But the immediacy of when users expect those settings to activate are different.

Using these controls in the right context will make your user interface intuitive to use. But using them in the wrong context can cause users to wonder what went wrong.

Switches Are for Instantaneous Actions

Switches always indicate whether a setting is on or off. When users turn a switch to “on,” they expect an instantaneous action as soon as there’s a change in the visual cue. This cue change is what signifies “on,” not just for UI switches but real-world switches too.

When you flip a light switch on, you expect the bulb to light up in an instant. Any delayed effect or need for further action makes you think something is wrong.

Switches should never require users to press a button to apply the settings because a switch is a toggle button. When you require users to press a submit button, you confuse them because it’s not what they expect.

You should only use switches on settings that need to take effect instantaneously. If a setting requires a button press before it can take effect, you should use a checkbox instead.

Checkboxes Require a Button Press

A checkbox does not apply the settings at an instant like a switch. Instead, it’s has a submit button and takes effect after the user presses it. Requiring a button press allows users to review their settings before they commit. This requirement helps prevent accidental activation errors.

The visual cue of a checkbox is different than a switch. While “on” implies instance, a checkmark only indicates selection. This difference in signals means users expect a more immediate change with switches than checkboxes.

Checkboxes are useful for applying a batch of settings. With switches, users have to wait for the system to apply each setting one by one. Checkboxes allow the system to handle multiple setting changes at one time.

If the user changes a batch of settings often, checkboxes save more time. But if the user will change only a few settings often, switches work better.

Deciding Between Switch or Checkbox

When choosing between a switch or checkbox, focus on context, not function. Ask yourself whether a setting should take immediate effect or not. Ask yourself whether users need to check their settings before they apply them.

Many real-world objects have similar functions. But similarity doesn’t mean they’re a fit for any occasion. There are subtle differences that come into play for a specific context. These differences are details that designers should never ignore, or they’ll end up misusing the object.

Toolkits