Generated UI comes back as the average
Figma pulled Make Designs after it drew something close to Apple's Weather app. The lesson outlasts the feature: generation without a point of view returns the most familiar answer.
Ask a model for a weather app and you get the weather app. This month that stopped being a thought experiment. On July 2, Figma switched off Make Designs, a week after announcing it at Config, because Andy Allen had asked it for a weather app and got back screens very close to Apple’s Weather. Figma said the feature leaned on off-the-shelf models and a design system it hadn’t checked carefully enough.
Most of the commentary has been about copying. Figma was right to pull it, but copying is the symptom.
The most likely answer
A model asked for “a weather app” returns the most likely weather app, and the most likely weather app is the one everybody has seen. That isn’t a bug in one feature. Generation does it whenever nobody gives it a point of view.
Anthropic shipped Artifacts twelve days earlier, on June 20: ask a chat window for an interface and a working one appears beside the conversation. Ask it for a dashboard and you get a competent one, with cards, a line chart and a sidebar, everything legal and nothing chosen.
Better models won’t change that on their own. Generated UI will get more correct and stay familiar, because distinctive means unlikely, and a model is built to be likely.
Where the designer goes
So the designer’s work moves up a level, from drawing the screen to deciding what the model is allowed to say: which components exist, how they combine, and what this product does that no other product does, written down clearly enough that a model can follow it.
That’s harder than drawing. A screen can be good by accident. A set of constraints that makes every output good has to be designed deliberately, and when it works nobody sees it. It is also a call someone has to own, which is the argument I made about who decides last summer.
Figma’s statement put some of the blame on the design system the feature used. That’s the right place to look. If a tool can only produce the average, a design team’s value is its distance from the average: its taste, written down and enforced.