Design, before Any Software · Chapter 06
The weight of a page is a design decision
1:49 · Narrated with a synthetic voice. Captions are available in the player.
Read the transcript
Real screens. Design at three hundred and sixty pixels wide and test on the cheapest phone you can borrow, outdoors, because shrinking a desktop layout hides the faults while expanding a phone layout exposes them. And remember that page weight is a design decision rather than an engineering one. A developer can compress an image. A developer cannot decide that the page does not need a full width photograph, three font families and an animated background. A three megabyte hero image takes about fifteen seconds on a connection a great many readers have, and ten seconds is the limit of held attention. On a prepaid data pack, a decorative background is money somebody paid. Every screen also ships in at least six states, and almost every review looks at one of them. Empty, one item, far too many, loading, error, and offline. The ones nobody designs ship as a blank rectangle and the words something went wrong. An empty state is the first screen a new user ever sees, so it should say what belongs there and offer the action that fills it. An error message has three jobs: what happened, why if you know it, and what to do next. And build with the longest realistic values, because a button sized to fit the English word save will not fit its translation.