Mode (user interface)

Content sourced from Wikipedia, licensed under CC BY-SA 3.0.

Mode in user interfaces means a state where inputs are treated according to different rules. When a mode is active, what you type or click can have a different effect than in another mode.

Modal vs modeless
- Modal: the interface uses different rules in different modes and you usually have to notice and confirm the current mode.
- Modeless: the same rules apply all the time, aiming to avoid mode errors where input is interpreted differently than you expect.

Locus of attention
People notice a mode more easily if the change is caused by them or if the interface clearly signals the new state where you interact. If your focus moves to another part of the screen, you might miss the current mode and make errors.

Problems with modes
- Mode errors can be startling and frustrating.
- Changes in state you don’t notice, or forgetting the current mode, lead to wrong actions.
- Focus stealing (a sudden change interrupts your task) makes things worse.
- Modes are sometimes used to force confirmation for dangerous actions, but critics say this can lead to habituation. Undoing actions is often a better solution.

When modes can help
- Modes can restrict dangerous or destructive actions or help with powerful tasks (like painting tools) when a user actively maintains the mode.
- Quasimodes are modes that stay active only while you hold a key or keep an action pressed.

Quasimodes
- Examples: holding Shift or Ctrl to apply a temporary function.
- Release without acting, and the interface returns to neutral.
- Quasimodes make actions predictable, so you don’t have to remember a separate mode state.
- StickyKeys can turn quasimodes into full modes, which helps some users but can raise risk of mode errors for others.

Tips and design choices
- Place modal controls near the trigger to keep them understandable.
- After finishing the task or canceling, return to the previous state to reduce disruption.
- Lightbox-style modals emphasize the dialog but can block normal work.
- Many designers prefer modeless interfaces, but some tasks still benefit from clear, well-managed modes.

History and viewpoints
- Larry Tesler campaigned against modes, promoting modeless designs.
- Jef Raskin argued strongly against modes and designed modeless systems like the Canon Cat and Archy.
- Some modern interfaces use cues (like a dimmed background) to make modal dialogs clearer, while still trying to minimize disruption.
- For mistakes, offering undo and easy exits is often better than forcing users through a modal confirmation.

Bottom line
Modes describe when inputs mean different things. Modeless designs avoid that complexity, but modes can be useful for focusing attention or preventing harmful actions if they’re clear, easy to exit, and well placed in the workflow.