Designing for the In-Between

Transitions, loading states, and empty moments are part of the product, not gaps around it.

Design the pause

I used to treat these moments as cleanup work for the end of a project.
That usually meant a spinner, a generic empty message, and a transition that technically worked but gave no sense of what was happening.

The in-between is where people decide whether a product feels trustworthy.
If a save takes a moment, the interface should explain that work is happening.
If there is no data yet, the empty state should help someone understand what belongs there and what they can do next.

When these edges receive the same care as the main path, an interface begins to feel calm and considered.
The experience does not become slower or more elaborate; it simply becomes easier to read.

Include the real journey

Now, when I sketch a flow, I include the pause after the action, the first visit before there is data, the failed request, and the return journey after an interruption.
Those are not edge cases to hide from the design.
They are part of the real product.