Layer-Based Design Is Dying

There's a quiet crisis in design tools that nobody talks about enough. Open any file and you'll find layers nested inside layers, auto-layout frames wrapping other frames, components with 12 levels of overrides, all to ship a set of assets that might get ignored in the first design review.

The Pixel-Perfect Trap

Design culture has spent two decades glorifying precision. Getting the padding right, aligning every element to an 8pt grid, arguing over border-radius values in Slack, these became the markers of a good designer. And they made sense at a time when everything had to be hand-coded and every pixel had consequences. That time is ending.

The obsession with pixel perfection isn't craftsmanship anymore. It's avoidance. It's easier to spend an hour tweaking a shadow than to sit with a hard problem and figure out if the screen should even exist.

What Design Should Actually Be Doing

Design is problem solving first. Every other skill, layout, typography, component structure, is in service of that. But layer-based design inverts the priority: the tool becomes the work, the file becomes the deliverable, and the actual question (does this solve something for a real person?) gets pushed to the end of the process.

The best design decisions are semantic, not syntactic. "This flow needs to feel low-friction" is semantic. "This button needs 16px horizontal padding and a 2px border" is syntactic. Both matter, but only one should be taking up the majority of a designer's thinking time.

Design Systems Changed Everything. AI Is Finishing the Job.

When design systems became mainstream, they quietly made a lot of layer-level decisions irrelevant. In the majority of cases, if a component already exists, spacing is already defined and colour tokens are already set, then why is a UI designer still manually building frames from scratch?