Context-sensitive user interface¶

Adapt available commands, presentation, or feedback to the application state, current object, user selection, mode, or task context.

Version: v2 · 2026-09-19 · History
Domain-specific #: 3883
Domain group: Professional & Organizational Practice
Origin domain: Human-Computer Interaction (HCI)
Subdomain: Adaptive and Contextual Interfaces → Human-Computer Interaction (HCI)

Core Idea¶

A context-sensitive interface changes options or feedback according to the state and object currently active for the user. The system maps a context vector to a filtered, reordered, or altered set of controls and cues, then updates that mapping as state changes. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

The load-bearing residual is not the broad topic of human computer interaction. It is state-to-interface adaptation with interaction consequences, not a static personalized layout.

How would you explain it like I'm…

Buttons That Know What You Tapped

When you tap on a picture, the app shows buttons for pictures, like 'crop'. When you tap on words, it shows buttons for words, like 'copy'. The screen changes its choices based on what you're doing. That's a context-sensitive user interface.

Menus That Change With What You Do

A context-sensitive user interface is a screen or program that changes which options or messages it shows based on what you're doing right now. For example, right-clicking a file shows file choices, and right-clicking text shows text choices. This saves you from digging through lots of options that don't apply. A good one still lets you find hidden options and fix things if it guesses your situation wrong. It's different from a screen that just looks the same for you every time because you set it up that way.

State-Adaptive Interface Controls

A context-sensitive user interface adapts its available options, presentation or feedback to the current state and the object the user is working with. The system maps the current context, such as which object is selected or what mode the program is in, to a filtered, reordered or changed set of controls and cues, and updates that mapping as the state changes. This differs from a static personalized layout, which doesn't change with the current state, and from simple responsiveness, like fast reactions or resizing to fit a screen. Having many modes isn't enough either; the controls have to actually adapt. Good designs keep commands discoverable, explain why options are unavailable, and let users recover if the system misjudges the context.

A context-sensitive user interface conditions some aspect of interface availability, presentation or feedback on the user's current state and active object, rather than keeping it invariant. The system maps a context vector to a filtered, reordered or altered set of controls and cues, and updates the mapping as state changes. Its identity is state-to-interface adaptation with interaction consequences, distinct from a static personalized layout, from an interface that merely has many modes without adapting controls, and from responsiveness in the sense of speed or layout reflow. Evaluating one requires enumerating the context variables and transitions, testing command discoverability and consistency in each state, exposing why options are unavailable, and providing escape or recovery when context is inferred wrongly. Benefits include fewer irrelevant choices, lower action cost, object-specific operations and timely feedback; failure modes include commands that become unreachable and inferred context that cannot be corrected.

Scope of Application¶

Context-sensitive user interface belongs to human computer interaction and is useful where the analyst can specify an interactive system with observable state, user focus or selection, a context model, and interface commands or feedback, then evaluate some interface availability, presentation, or feedback is intentionally conditioned on declared context rather than remaining invariant. The scope is broad within that domain but bounded by the need for some interface availability, presentation, or feedback is intentionally conditioned on declared context rather than remaining invariant. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.

Clarity¶

The abstraction clarifies a crowded vocabulary by making some interface availability, presentation, or feedback is intentionally conditioned on declared context rather than remaining invariant the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name Context-sensitive user interface can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated.

Manages Complexity¶

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Context-sensitive user interface. Context-sensitive user interface compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning¶

Identify the carrier. State what the elements, states, objects, or observations are: an interactive system with observable state, user focus or selection, a context model, and interface commands or feedback. Reject examples whose alleged carrier belongs to a different problem.
Lock the constitutive rule. Express some interface availability, presentation, or feedback is intentionally conditioned on declared context rather than remaining invariant independently of one notation or implementation.

Knowledge Transfer¶

Knowledge transfers strongly among subfields of human computer interaction because they reuse an interactive system with observable state, user focus or selection, a context model, and interface commands or feedback, The system maps a context vector to a filtered, reordered, or altered set of controls and cues, then updates that mapping as state changes., and enumerate context variables and transitions, test command discoverability and consistency in each state, expose why options are unavailable, and provide escape or recovery from mistaken inference.

Relationships to Other Abstractions¶

Current abstraction Context-sensitive user interface Domain-specific

Parents (1) — outgoing typed relations

Context-sensitive user interface is a kind of Contextual Mode Switching Prime

What makes it its own entry: state-to-interface adaptation with interaction consequences, not a static personalized layout.

Hierarchy paths (2) — routes to 2 parentless roots

Context-sensitive user interface → is a kind of Contextual Mode Switching → is a kind of Adaptation

Show alternative path (1)

Neighborhood in Abstraction Space¶

Context-sensitive user interface sits in a crowded region of the domain-specific corpus (33^rd percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Interface & Interaction Design Methods (20 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-25