UI

UI work covers components such as navigation, forms, buttons, menus, typography, icons, states and responsive layouts. It is closely related to, but not identical with, user experience. In practical terms, UI belongs to the structure and interaction layer. Knowing that layer is important because it tells you what the term can change, what it cannot change, and where to look when something behaves unexpectedly.

The common mistake is to use UI as if it also meant UX. That blurs two separate decisions and usually sends troubleshooting in the wrong direction. A better test is practical: Evaluate UI states as well as appearance: default, hover, focus, disabled, loading, error and success can all matter.

In day-to-day work, UI matters when the concept needs to be identified precisely instead of being grouped with a nearby term. The practical value is not the vocabulary itself; it is being able to identify the right control, file, setting or decision when the concept becomes relevant.

Buttons, menus, form fields, cards and navigation are UI elements: the visible and interactive parts through which people operate a product. That example is useful because it turns the definition into something you can recognize, test and discuss with other people working on the same project.

Use these references when you need documentation-level detail, specifications or product-specific behavior beyond the plain-English explanation above.