A static mockup answers one question well: what does this look like when everything goes right, at one screen size, with content of a convenient length. That is a small fraction of what the interface will actually be, and the remaining fraction is where the disagreements happen, usually during implementation, usually late.
Four things a frame cannot show
- Real content. Names are longer than the placeholder, titles wrap to three lines, and some users have no avatar. Designs tuned to ideal content break on the first real record.
- States. Loading, empty, error, partial, and stale are most of the states a user experiences and almost none of the frames produced.
- Motion and timing. Whether a transition feels responsive or sluggish cannot be judged from a still image, and neither can whether a spinner is needed at all.
- Responsive behaviour. Three fixed breakpoints hide what happens between them, which is where most users are.
Prototype where it will ship
The most reliable correction is to build the risky part in the real medium early, with real data, at real speeds. This does not mean designers must write production code. It means the questions that only the medium can answer should be asked in the medium, with whatever fidelity gets an answer fastest.
Modern tooling makes this cheaper than it was: component libraries make a rough build fast, and generation tools can produce a working screen from your real primitives in minutes. The output is not production quality and does not need to be. It needs to be honest about behaviour.
Design the empty state first
A reliable trick for getting to the important decisions quickly: start with the empty state, then the error state, and only then the ideal state. Designing the empty state first forces a conversation about what the feature is for and how a new user gets to value, which is the conversation the ideal-state mockup lets everyone avoid.
Every product is mostly empty, loading, or broken for someone right now. Those screens deserve the same care as the marketing screenshot.
What static frames are still best for
Exploring visual direction, aligning stakeholders on hierarchy, and working through typography and spacing are all faster in a design tool, and pretending otherwise wastes time. The argument is not that mockups are obsolete. It is that they are the beginning of the conversation and should stop being treated as the specification.
Join the conversation
Discussion0
Join the conversation. Sign in to leave a response or reply to comments.