Continuity transition

Also called container transform or visual continuity

A transition where one element keeps its identity as it changes role, like an “Add to cart” button that becomes a progress bar, then a checkmark.

What is Continuity transition?

A continuity transition keeps a single element on screen through a whole sequence of changes. The button you pressed stays where your eyes already are and turns into the loading state, then into the result. Nothing disappears and nothing new pops up somewhere else, so people never have to search for what happened.

Use it for actions with a few clear stages: Add to cart, Send, Pay, Upload, Follow. Material Design calls a related pattern a container transform, where a card or floating button expands into the screen it opens.

Make each stage readable on its own: the label, the progress, and the confirmation. Keep the element in the same position, change its size only as much as each stage needs, and leave the result up for a second or so before resetting. Announce the outcome in an aria-live region, because screen readers do not describe the shape change.

Often confused with

Morph
A morph is a single shape change. A continuity transition chains several, keeping one element on screen across the stages of a task.
All terms

Morph

A transition where one shape smoothly changes its size, corners, and contents into another, like a small pill growing into a full card.

Loading state

The view a screen shows while its data is on the way, designed together with the outcomes that follow: loaded, empty, or error.

Micro-interaction

A small moment of feedback around a single action, like a heart that bursts when tapped or a copy icon that turns into a checkmark.

Optimistic UI

A pattern where the interface shows the result of an action right away, before the server confirms it, and rolls it back if the request fails.