When design stops being decoration

Early on, design felt like the layer you put on top of an app once the app worked. Pick a font, pick a color, round some corners, ship. I do not think that anymore.

The thing that changed my mind was watching the same engineering decision get easier or harder depending on whether the design was in place first. A screen that has been laid out properly tells you what state it needs. A screen that has not been laid out yet asks you to invent state speculatively, and most of the state I have ever invented speculatively has been wrong.

So now I treat design as architecture. The wireframes are the rough draft of the data model. The empty states are the rough draft of the error handling. The transitions are the rough draft of the loading logic. By the time I open the editor, half of the engineering decisions are already pinned down, and the half that remain are the ones I actually want to spend time on.

This is, I think, the unfair advantage of building both halves yourself. You do not have to translate between two people who are looking at the product through different lenses. You only have to be honest with yourself about which lens you are using when, and switch when the work asks you to.