User Interface (UI)

Technical explanation

A UI may be graphical, command-line, voice-based, conversational, gestural, or multimodal. Its implementation connects information architecture, interaction states, input and output controls, visual hierarchy, accessibility semantics, error handling, and system feedback.

Business relevance

A clear, accessible UI reduces errors and learning effort, supports task completion, and makes underlying capabilities usable. Interface inconsistency raises support cost and erodes trust.

Implementation example

A design system standardises form controls, validation messages, focus states, and component behaviour across a customer portal while engineering preserves semantic HTML and keyboard operation.

Limitations and common misconceptions

UI is not synonymous with UX: a polished interface can sit within a poor end-to-end experience. Components must be validated in context, and visual consistency alone does not ensure accessibility or usability.

Topics

Sources