S/02

Interface design

Screens with the awkward states drawn too — half-empty, mid-upload, wrong password, four hundred rows and counting.

FlowsStatesSpecs

The states nobody screenshots

A portfolio full of happy-path screens is a portfolio of screens your users will rarely see. The interesting design problems live in the states that are hard to make look good: the empty dashboard on day one, the list with four hundred rows, the upload that failed at 80%, the name that is far too long for its container.

Those get drawn here as a matter of course, because they are what your product actually feels like to use.

How it usually runs

Six weeks for a full product engagement. Week one is listening, week two is structure on paper, weeks three to five are full-fidelity work, and week six is handover.

What you get

Source files, a component library with every state documented, exported assets, and a written specification covering behaviour and edge cases.

What is included

Full flows drawn with real content, not lorem ipsum
Every state designed — empty, loading, partial, error, overflowing
A written specification covering behaviour, not just appearance
Keyboard paths and focus order defined before handover

Two project slots open from September

Have you got something that deserves doing properly?

Tell me what is broken, who it is breaking for, and what happens if it stays that way. That is enough for me to come back with a scope and a number.