A user interface is the visible and interactive surface through which a person gives commands to a product and receives information or feedback from it.
Open almost any software product and you are looking at a user interface.
The interface translates between human intent and system behavior. A person selects, types, drags, taps, speaks, or issues a command. The system responds with information, feedback, a state change, or another choice.
Menus, tabs, breadcrumbs, search, sidebars, and links help users move through the product.
Buttons, fields, checkboxes, radio buttons, selectors, uploads, and editors let users provide information or trigger actions.
Tables, cards, text, charts, badges, notifications, and status indicators communicate information.
Modals, panels, accordions, drawers, and sections organize related content and actions.
Loading indicators, confirmations, disabled states, validation, warnings, and errors tell users what the system is doing.
Uses visual controls such as windows, icons, buttons, menus, and pointers. Most desktop, web, and mobile products use a GUI.
Users interact by entering text commands. CLIs can be efficient for expert or developer workflows.
Users interact using spoken language, as with voice assistants and voice-controlled devices.
Users tap, swipe, pinch, drag, or use physical gestures to control the system.
Some products combine multiple interface types.
The user interface is the actual interaction surface.
UI design is the discipline used to decide how that surface should look and behave.
For example, the search field, filter controls, table, and empty state in a dashboard are parts of the interface. Choosing their hierarchy, component variants, spacing, and visual states is UI design work.
The interface is one part of the user experience.
UX also includes whether the product solves the right problem, how the journey is structured, how fast the system responds, how errors are handled, and whether the user trusts the outcome.
The interface is where much of the experience becomes visible, but it is not the entire experience.
A strong interface generally makes five things clear:
Consistency also matters. Similar actions should use familiar controls and behavior across the product.
An interface is not a static screenshot.
Take a file upload control. It may be empty, selecting, uploading, paused, completed, failed, retried, blocked by permissions, or rejected because of file size.
Each condition changes what the user sees and what they can do. Designing only the default state leaves part of the interface undefined.
Minimal visual clutter is not useful if users cannot find what they need.
Different patterns for the same action make the product harder to learn.
If an action appears to do nothing, users may repeat it or lose confidence.
Too much undifferentiated information makes scanning and decision-making difficult.
An interface is not effective if meaningful groups of intended users cannot operate it.
Yes, when people use its controls, navigation, forms, or content to interact with a system or service.
No. GUI is one type of user interface. A command line or voice assistant is also a UI.
A component is one reusable building block. An interface combines many components, content, and states into a usable surface.
A user interface is the conversation surface between a person and a system.
The better that surface communicates actions, state, feedback, and consequences, the less effort the user spends trying to decode the product.
UI design · User experience · Interaction design · Usability · Product design
For a deeper walkthrough of interface types, components, and principles, read Figr’s user interface design guide.