Refactoring UI

About the book

Refactoring UI is a design book by Adam Wathan and Steve Schoger, aimed at developers and product builders who write code more comfortably than they choose typefaces. It treats visual design as a set of learnable decisions and works through those decisions at the level of concrete screens: spacing, hierarchy, color, depth, and the small adjustments that separate a working layout from a polished one.

The book's premise is that most interface problems come from a handful of recurring causes, and that naming those causes makes them fixable. It favors before-and-after examples and rules of thumb a reader can apply during a build over design as a body of theory to absorb. That orientation toward the practical is the book's main appeal and also the thing to weigh before buying.

How to read it

Approach this as a reference and a diagnostic tool rather than a linear argument. The material is organized around recurring problems, and the value comes from returning to a section when a specific screen looks wrong. Read a short stretch, then apply it to something you are actually building; the examples land better when you have a real layout in front of you.

The difficulty is low for anyone comfortable with front-end work, though the book assumes some familiarity with how interfaces are assembled. Its advice is opinionated and example-driven, so treat individual rules as defaults to test rather than laws. Expect to disagree with some choices and to adapt others to your product's context.

Who it suits

Developers who can ship a functional interface but want it to look intentional will get the most from this. So will founders and solo builders without a designer on hand, and designers who want a shared vocabulary for giving feedback to engineers. Readers seeking a rigorous treatment of design theory or accessibility standards should look elsewhere; this book is about visual craft and fast, concrete improvement.

Reading considerations

The guidance is oriented toward the web and product interfaces of its era, so some examples and conventions may feel dated as tooling and platform norms move on. Treat its rules as starting points and verify accessibility and usability against current standards rather than relying on the book alone.