Designing software that disappears

Zealo is used between sets. The person is tired, the rest timer is running, and the screen has one job: record what just happened and show the next set. Anything else is a tax.

That constraint shows up in client work too. A clinician between patients, a founder between meetings, an operator on a warehouse floor. The setting tells you how much interface you are allowed to have. Usually it is less than the first mockup.

Remove steps until the task is the interface

We prototype the difficult moment before the marketing screen. If logging, confirming, or understanding a result takes too long, we cut a step. Then we cut another. Motion stays only when it explains a change: a screen that arrived, a value that updated, an error that needs a decision.

Performance is part of this. A beautiful screen that hitches on open is a screen people learn to distrust. Native tools are how we keep the promise on iOS.

Words do the same job as layout

Buttons say what will happen. Empty screens say what to do next. We do not write “Submit” when the action is “Send the brief,” and we do not write “Oops” when the action failed for a reason the person can fix.

Software disappears when the person can finish the task and put the phone down. That is the standard we design toward.