Building for the In-Between

Most interface mockups depict settled moments. The data has arrived. The image is sharp. The button is ready. But people spend a surprising amount of time between those moments: loading, waiting, moving, losing connection, returning.

Those intervals are not empty. They are where a digital product explains what kind of thing it is.

Transitions reveal the model

A good transition does more than smooth a change. It shows the relationship between two states. A card expands into an article because the article was already latent inside it. A panel moves aside because the space behind it existed all along.

When motion contradicts structure, an interface feels decorated. When it reveals structure, the interface becomes easier to understand.

Waiting deserves direction

Progress indicators are promises. Some can be precise; others can only acknowledge uncertainty. The wrong indicator quietly breaks trust—a determinate bar that freezes at ninety-nine percent is worse than an honest, breathing signal.

We can design waiting as a moment of orientation: preserve the last useful state, explain what is happening, and let people continue where possible.

Return is part of the path

Products often celebrate arrival and neglect return. Yet a returning visitor carries context, expectations, and unfinished intent. Remembering scroll position, restoring a draft, or simply making visited material feel familiar can turn a collection of pages into a place.

The in-between is where continuity lives. Designing it carefully is how software stops feeling like a sequence of screens and begins to feel like a world.