The Investor's Shelf — one book
Refactoring UI

Refactoring UI

Adam Wathan, Steve Schoger
2018
T3 218 pages · about 3h 38m to read OL23977983Wgoodreads

Where most design books stay in the abstract, this one opens with specific visual decisions: spacing scales, type hierarchies, color palette construction, shadow systems. Written by developers who taught themselves visual design, it's unusually practical and works equally well for product designers who want stronger visual intuition.

Summary

Wathan and Schoger wrote this for developers who need to design interfaces and have no design training. It is organised as a set of specific, applicable tactics rather than as design theory, with before-and-after examples for each.

The substantive advice covers hierarchy, spacing, typography, colour, depth and imagery. On hierarchy they argue that most amateur interfaces fail because everything has the same visual weight, and they give concrete methods: use font weight and colour rather than size to create distinction, de-emphasise supporting text rather than emphasising primary text, and label content only when the label carries information. On layout they argue for starting with too much white space and removing it, for sizing elements by content rather than filling the available width, and for designing the mobile layout in a desktop-width window to avoid cramped thinking. On colour they set out how to build a palette using HSL, why lightness must be varied along with hue, and how to generate the eight to ten shades of each colour a real interface needs. On typography they cover choosing typefaces, line length, line height and the specific problem of vertical alignment.

The book is compact, entirely practical, and it produces visible improvement quickly, which is why it circulates among founders building their own products. It teaches tactics rather than design judgement, so it will not make a reader a designer. Its aesthetic is specific to the mid-2010s web application style, and interfaces built strictly by its rules look similar to each other. It also predates the current design systems and component library practice, though the underlying principles about hierarchy and spacing are not affected.

Key takeaways 7

  1. Interfaces fail most often because every element has equal visual weight, and establishing hierarchy is the single highest-value change.
  2. Hierarchy should be created with font weight and colour rather than with size, because size differences quickly become crude.
  3. De-emphasising secondary content works better than emphasising primary content, since it avoids inflating the whole interface.
  4. Start a design with more white space than seems necessary and remove it, because the common failure is cramped layout rather than sparse layout.
  5. A usable colour system needs eight to ten shades of each hue, and generating them requires varying saturation and lightness together rather than mixing with grey.
  6. Elements should be sized to their content rather than stretched to fill the available width.
  7. Choosing a typeface matters far less than setting line length, line height and weight correctly, and most typography problems are spacing problems.

Who should read it

Founders and developers who build product interfaces without a designer and need immediately applicable tactics.

Where it sits in the reference 2

Business themes
Business themes

Who recommended it 2

Book recommendations listed on their Good Books profile · aggregator only
Book recommendations listed on their Good Books profile · aggregator only

Similar books 6

Chosen by shared topics, the entries that hold them, and the people who recommended both.

Don't Make Me Think
Don't Make Me ThinkSteve Krug
Sprint
SprintJake Knapp, John Zeratsky
The Design of Everyday Things
The Design of Everyday ThingsDonald Norman
100 Things Every Designer Needs to Know Abou
100 Things Every Designer Needs to Know About PeopleSusan Weinschenk
About Face: The Essentials of Interaction De
About Face: The Essentials of Interaction DesignAlan Cooper
Articulating Design Decisions
Articulating Design DecisionsTom Greever