Skip to content
← All field notes

Interface notes

Designing the one-handed moment

A field note on glanceability, reach, and building interfaces for the imperfect moments where software is actually used.

4 min read

People rarely use software in the clean, centered posture shown in product mockups. They use it while walking, holding coffee, switching trains, listening for a child, or trying to remember the thing they opened the app to do.

The useful design unit is not the screen. It is the moment of divided attention.

Glance before gesture

Before asking what someone should tap, ask what they need to understand. Hierarchy earns its keep when a half-second glance is enough to recover context.

That leads to a few durable rules:

  1. Put state before controls.
  2. Make the primary action physically obvious.
  3. Use color to reinforce meaning, never to carry it alone.
  4. Let secondary information wait its turn.

Reach is part of information architecture

On mobile, importance and reach should usually agree. High-frequency actions belong where a thumb naturally rests. Rare configuration can live farther away. Destructive actions deserve both distance and friction.

This sounds mechanical, but it changes the emotional quality of a product. An interface that meets the hand where it is feels calm. One that constantly makes the hand negotiate feels demanding.

The goal is not fewer features. It is less choreography between intention and result.