Skip to content
BENIBIX Learn

Component State

Design🖼️ User InterfaceUI Basics

Also known as Hover State, Pressed State, Disabled State, Focus State

How a part looks right now: resting, hover, pressed, focused or off.

Think of it like

It is like a light switch. It looks different when it is on, off or broken.

Example

A Save button shows no change when pressed. People tap it three times, so the team adds a pressed look.

Why it matters

States are the feedback that tells people a part heard them, or that it cannot be used yet.

Definition

A component state is how a part looks at a given moment of use. A button has a resting state, a hover state when the pointer is over it, a pressed state, a focus state when reached by keyboard, and a disabled state. The app picks the state, not the designer. Each state must be designed, or people cannot tell what is going on.

Try it

Resting. Nothing is happening yet.

The app decides

Point at the button, press it, or reach it with Tab. The name underneath follows.

Common mistake

Forgetting the focus state. People who use a keyboard then cannot see where they are.

Key takeaways

  1. 1
    The app picks it. Based on what is happening.
  2. 2
    Design every one. Rest, hover, press, focus, off.
  3. 3
    Never skip focus. Keyboard users need it.

Learn it properly