Designing for the next tap
Why the best interface decisions often happen before a screen is drawn.
Good digital products are useful in a specific situation. Beginning there — with the moment someone reaches for the phone — makes the choices that follow far clearer: what to include, what to leave out, and how to make the whole thing feel calm.
Start with the human moment
Before a single screen exists, you can usually name the three or four states a person will actually be in when they open the app. Tired. In a hurry. Halfway through something else. Design for those and the interface stops being a menu of everything the software can do, and starts being an answer to a question.
The point is not more interface. It is the right amount of interface.
The next tap is the only one that matters
A screen has one job: make the next action obvious. Everything competing with that action is a cost, even when it is individually reasonable. The discipline is not adding less — it is deciding what the screen is for and letting that decision win every argument.
- Name the single action the screen exists to support.
- Give it the most visual weight, without exception.
- Move anything that is only occasionally useful one layer down.
- Delete whatever survives that process without a defender.
Then make it dependable
Design, performance and accessibility are not separate stages of the work. They are qualities of the same product decision, and they arrive together or not at all.