What is Interaction Design?

TL;DR

• Interaction design defines what happens between a user action and the system’s response.
• It covers inputs, feedback, state changes, transitions, constraints, and recovery.
• Interaction design is broader than animation and narrower than the full UX discipline.
• A strong interaction makes the result of an action understandable and predictable.
• Loading, disabled, success, error, and recovery behavior are interaction-design decisions.

What does interaction design actually mean?

A static screen can show where a button is. Interaction design explains what happens when the user presses it.

Consider a “Freeze card” action in a banking product.

Good interaction design has to answer questions such as:

• Does the action happen immediately or require confirmation?
• What feedback appears after the tap?
• Does the button become disabled while the request is processing?
• What happens if the network fails?
• How is the frozen state represented afterward?
• Can the action be reversed?

The interaction is the sequence of cause and effect, not only the visual appearance of the control.

The basic interaction loop

Many digital interactions can be understood as a simple loop:

1. Intent: The user wants something to happen.
2. Action: They click, tap, type, drag, speak, or otherwise provide input.
3. System response: The product processes the action.
4. Feedback: The interface communicates what happened.
5. New state: The product and available next actions change.

If one part of that loop is unclear, the user can lose confidence.

What do interaction designers think about?

Inputs

What actions are available, and which input methods can trigger them?

Rules and constraints

When is an action available, unavailable, destructive, reversible, or permission-dependent?

Feedback

How quickly and clearly does the system acknowledge the action?

State

How does the interface represent what is true before, during, and after the interaction?

Transitions

How does the interface move between states without disorienting the user?

Recovery

What happens if the action fails or the user changes their mind?

Interaction design vs. UI design

UI design deals with the visual and interactive interface layer. Interaction design focuses more specifically on behavior over time.

The disciplines overlap heavily.

A UI designer may define the appearance of a dropdown. Interaction design defines how it opens, closes, responds to keyboard input, handles focus, behaves when disabled, and confirms a selection.

Interaction design vs. UX design

UX design is broader. It can include research, information architecture, flows, usability testing, and the overall experience.

Interaction design is one discipline used to make that experience coherent at the action-and-response level.

Interaction design vs. animation

Animation can support an interaction, but interaction design is not synonymous with motion.

A perfectly timed transition is useless if the action itself is confusing or lacks recovery.

Motion should clarify relationships, status, or change rather than exist only for decoration.

How do you design an interaction?

1. Define the user’s goal.
2. Identify the action that should express that intent.
3. List important states before and after the action.
4. Define constraints, permissions, and invalid conditions.
5. Specify immediate feedback.
6. Map success, failure, retry, undo, and cancellation where relevant.
7. Prototype the interaction at enough fidelity to test the uncertain parts.
8. Check keyboard, focus, touch, and accessibility behavior.
9. Validate the full interaction in the context of the user flow.

Common interaction-design mistakes

No immediate feedback

Users should not have to guess whether the system registered their action.

Motion for decoration

Animation should support comprehension rather than slow users down or distract them.

Missing disabled and loading behavior

Repeated taps and duplicate submissions often come from undefined intermediate states.

Inconsistent behavior

The same interaction pattern should not behave differently across screens without a reason.

Designing only success

Failure and recovery are part of the interaction.

Frequently asked questions

What is a micro-interaction?

A micro-interaction is a small, focused interaction around one action or status, such as liking a post, toggling a setting, or showing save confirmation.

Does interaction design require prototyping?

Not every interaction needs a high-fidelity prototype, but prototyping is useful when timing, sequence, states, or unfamiliar behavior need validation.

Why are states important in interaction design?

Because the available actions and meaning of the interface often depend on what the system currently knows or is doing.

The bottom line

Interaction design asks: when the user does this, what should the product do next, and how will the user understand it?

That cause-and-effect clarity is what makes software feel responsive rather than mysterious.

Related terms

UI design · UX design · User experience · User interface · Usability

Relevant Figr resource

For concrete product examples, read Interaction Design Examples.