Product design
Designing something people use repeatedly is a different job from designing something they visit.
We design digital products: the flows, screens and states behind an app, a platform or a tool. The work is decided by repeat use, where delight matters less than not being in the way.
A marketing site is judged on the first impression. A product is judged on the hundredth interaction, when the novelty is gone and someone simply wants the thing done.
The states nobody puts in the presentation
Empty, loading, error, partial, offline, too much data, not enough. These are most of the real experience and almost none of the pitch, and a product designed only in its happy path breaks the first week it meets a customer.
Every flow is designed to its ends: what happens when someone abandons halfway, changes their mind, or comes back three weeks later on a different device.
A system, so the tenth screen is not a new argument
Components carry their states and their rules, so a new screen is assembled from decisions already made. That is what keeps a product coherent as it grows past the team that started it.
We work in the build's own terms, handing over spacing, behaviour and edge cases specified rather than implied, because the gap between a design and a product is filled by whoever is nearest at the time.
Want a product that still makes sense on the hundredth use?
Let's talk.
