Skip to content
BENIBIX Learn

UI Components Basics

Level 1 · Parts and their states

What a UI component is, and why one part is built once and reused. Variants the designer picks, and the states that the user causes.

Course contentsLesson 1 of 14

After this lesson you can

  • Say what a UI component is
  • Tell a variant from a state
  • List the five common states

10 mincovers 4 glossary entries

What a UI component is, and what a state is

A user interface, or UI, is the part of an app you see and touch. It is built from parts called components: a button, a text box, a menu. Each one is made once and reused. A big app may show the same button on 200 screens, and all 200 come from one main part.

That is the point of a component. Change the main one, and every copy changes with it. Make the corners rounder, and 200 buttons get rounder corners at once. Without components, someone has to find and fix every copy by hand, and a few always get missed.

A variant is one version of a part. A button might come in a filled version for the main action and a plain version for the rest. The designer picks the variant when they place the button. It does not change while the app runs.

A state is how a part looks right now, because of what the user is doing. Most parts have five: resting, hover when a mouse is over it, pressed, focused when the keyboard has reached it, and off when it cannot be used. The user causes the state. The designer only draws it.

Every state needs its own look. A pressed button that looks the same as a resting one feels broken, because nothing answered the press. A focused button with no outline leaves keyboard users lost on the page. Drawing only the resting state is the most common gap in a design file.

The off state needs care too. A gray button that cannot be pressed should say why, or the user is stuck guessing. Often it is better to leave the button on and show a clear message when it is pressed too early.

This course stops at the parts themselves. It does not cover research with users, page layout across screen sizes, or building a full design system. Those are subjects of their own. Here you learn what each part is for, and how to pick between the ones that look alike.

Pick a version, let the app pick the look

You pick: version

The app hands out: look

Filled + Resting. Still one part.

The left picker is yours. The right one belongs to the app.

The left picker is yours, as the designer. The right one is what the app does on its own as people use it.

The designer picks one variant. The user then moves it through five states, and each one needs its own look.

Worked example

A bank app changes one button

A bank app shows its main button on 140 screens. The team wants the corners 4 pixels rounder.

Every button is a copy of one main part, so the change takes a few minutes. Before they used components, a change like this took two weeks. It still missed 9 screens.

The words for this lesson4

Check yourself

How is a variant of a part different from its state?

Finished this lesson?

Marking it complete also marks its 4 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.