Designing for the small screen
The Phone
Award-winning work is almost always shown as a desktop screenshot and almost never seen that way. So: what survives the loss of a wide screen, what reliably breaks, and which kinds of site the jury marks down for it.
What breaks
Photographs Are What Fail on a Phone
The jury scores responsive behaviour separately, and 655 winners carry that mark. Almost everyone clears it — but the ones who do not are not scattered at random. Ranked by the share of each genre falling below 7.0:
The four worst are the four that lean hardest on photography — photo & video, photography, food & drink, events. The genres that never drop below 7.0 at all are the structured ones: corporate, technology, architecture, institutions, apps. A composition arranged across a wide screen has to be thrown away on a phone; a page built as a column simply gets narrower.
Read the pattern rather than any single figure: these are small samples — Photo & Video is 3 sites of 18. What carries the argument is that four picture-led genres sit at the top and five structured ones sit at zero, not the distance between any two of them.
Designed for the phone
What Phone-First Work Does Differently
Work built phone-first has its own award track, and what separates it from desktop work is not a matter of style. The differences are structural: what changes is how the thing is put together, not how it is decorated.
Content architecture leads at 3.8 times the desktop rate. On a wide screen an unresolved hierarchy can be hidden by putting things side by side. On a phone there is only one column, so the order things appear in is the design, and it has to be decided rather than arranged around.
The rest follows from it. Interface design runs high because phone-first work is assembled from components rather than composed as a picture. The about page appears as a named destination rather than a link in a footer, because there is no footer worth scrolling to. Startups are over-represented because a young company is likelier to have been designed for the phone first and the desktop after. Icons carry navigation that a wide screen would have spelled out in words.
Two traits barely exist in the desktop record at all: app style on 25%. Those are not tendencies, they are what phone-first work is — a set of screens with a system behind them rather than a page with a layout.
Recent phone-first winners
The mobile track publishes a jury score for only 9 of its 177 winners, so these are in the order the gallery lists them, newest first, rather than ranked. A score is shown where one exists.
Everything else, on a phone
How The Rest Of The Field Scores
The more useful question for most projects is not how to design an app. It is what happens to an ordinary site on a small screen — and that is marked. The developer award scores responsive behaviour as one of six axes, and 655 winners carry that mark.
Only 6% fall below 7.0. Responsive behaviour is the one thing this field has settled: it is no longer where sites are won or lost, because almost everyone clears it. That is worth knowing in the other direction too — doing it well earns nothing, and doing it badly is one of the few remaining ways to lose outright.
By kind of site
Mean responsive mark, 17 genres with at least eight marks between them. The scale runs from 6.5 to 8.0, which is where every genre sits — the spread between the best and worst kind of site is 0.44 of a point, so this is a narrow field with a real order inside it.
Apps comes out highest at 7.77 and Food & Drink lowest at 7.33. The pattern is not random: the genres at the bottom are the picture-led ones, where the desktop composition is the point and a phone has to throw most of it away. The genres at the top are the ones that were always going to be read in a column.
What to take from it
Two Different Briefs
If the work is phone-first, the decision that matters is the order of things, not the look of them. Content architecture is the trait that separates this category from everything else, and it is a decision made before anything is drawn.
If the work is an ordinary site that will mostly be seen on a phone — which is nearly all work — responsive behaviour is table stakes and will not distinguish it. The distinguishing question is what survives the loss of the wide composition: whether the argument still lands in one column, or whether it was only ever an arrangement.
177 phone-first winners from the mobile gallery, and 655 responsive marks from the developer award. 655 is not every winner — a further set carries no developer assessment at all, and those are excluded rather than counted as zero, which would drag the mean from 7.5 to about 5.3 and mean nothing.