How Interface Design Evolved from Skeuomorphism to Systems
Skeuomorphism, flat, Material, design tokens, multiplayer tools, generative AI. What each shift kept, what it lost, and where human judgment sits now.
Interface design has gone through half a dozen major shifts since the iPhone arrived in 2007. Each one fixed a real problem, then threw something useful away, and the next shift usually spent its first years getting it back.
Looking at the sequence as a whole is more useful than arguing about any single style. It shows which ideas keep returning and where the human part of design has moved.
Skeuomorphism: borrowing the physical world
Early iPhone apps looked like objects. Notes sat on yellow legal paper, the calendar had stitched leather, and the bookshelf had wood grain. This is skeuomorphism: digital elements styled after their physical counterparts.
It had a clear job. In 2007 most people had never used a multi-touch screen. Making a button look raised and a toggle look like a switch told them, before they touched anything, what could be pressed and what would happen. In Don Norman's terms, the textures were signifiers.
What it kept: strong cues for what is interactive, borrowed from objects people already understood.
What it lost: honesty and economy. Decoration grew beyond what was needed to signal function. Leather stitching does not tell you anything about a calendar. The visual weight also made interfaces harder to scale across screen sizes and harder to keep consistent between apps.
Flat design: iOS 7 and the purge (2013)
Microsoft got there first with its Metro language, which it called "authentically digital." But the decisive moment was Apple's iOS 7 announcement on 10 June 2013. Textures disappeared, replaced by thin type, translucency, layered motion and bright color. Jony Ive's line in the press release: "There is a profound and enduring beauty in simplicity, in clarity, in efficiency."
What it kept: content first, less chrome, interfaces that rendered cleanly on any screen density.
What it lost: signifiers. When everything is a flat rectangle of color, users cannot always tell a button from a label. Kate Moran's 2015 NN/g analysis of flat design documented this directly, noting that removing clickability cues can make users slower and less certain. She recommended "Flat 2.0," which keeps the flat look but brings back subtle shadows and layers.
Material Design: physics as a rule set (2014)
Google introduced Material Design at Google I/O on 25 June 2014, with Matías Duarte presenting. Its central metaphor was paper and ink. Surfaces had elevation and cast shadows, and motion followed physical rules. The team reportedly prototyped with actual paper to work out how shadows should behave.
Material was flat design with the signifiers put back, but with a crucial difference from skeuomorphism. Instead of imitating specific objects, it borrowed general physical behavior: things sit above other things, light comes from above, objects move with momentum.
It was also published as a full specification with components, not just a visual style. According to Google's own retrospective, more than a million products on the Android store were using parts of it within a year.
What it kept: clear hierarchy, honest depth, a shared vocabulary across platforms.
What it lost: some distinctiveness. When a single system is that easy to adopt, many products end up looking alike.
Design systems and tokens: design as infrastructure
Material showed that a design language could be shipped like a library. Through the mid-2010s, product teams started building their own. Brad Frost's Atomic Design (2016) gave the movement its framing, quoting Stephen Hay: "We're not designing pages, we're designing systems of components."
The next step was to make the smallest decisions (a color, a spacing step, a radius, a font size) into named, versioned values that both design tools and code could read. These are design tokens. The W3C Design Tokens Community Group worked for several years on a common format, and on 28 October 2025 it published the Design Tokens Format Module 2025.10, the first stable version. Tokens are JSON objects with a $value and a $type:
{
"color": {
"text-primary": { "$type": "color", "$value": "#1a1a1a" }
}
}
What it kept: consistency at scale, and a direct link between a design decision and the code that ships it.
What it lost: some of the craft of individual screens. When most decisions are made once in a token file, there is a pull toward assembling interfaces from parts rather than designing them for a particular moment.
Multiplayer tools: design becomes a shared document
Figma brought real-time multiplayer editing to design files, in the browser, in 2016. Evan Wallace's technical write-up (2019) explains the approach: inspired by CRDTs, but with a central server as the authority, which kept the system simpler than fully decentralized alternatives.
The cultural change was larger than the technical one. Engineers, PMs and researchers could now open the same file the designer was working in, comment directly on it, and inspect values. Design stopped being a handoff and became a shared, continuously visible artifact.
What it kept: the system thinking of the previous era, now with everyone looking at it at once.
What it lost: private space for bad first drafts. When every exploration is visible to the whole team, there is pressure to show only polished work.
Generative tools: the draft is free
Since around 2023, generative tools have been producing layouts, components and working prototypes from text prompts. Figma's Figma Make, announced in May 2025, is one example: describe a change or paste a frame, and it produces an interactive, code-backed prototype.
These tools sit on top of everything before them. They generate in the vocabulary of design systems, they often output tokens and components, and they work inside multiplayer files. Their main effect is economic. The first draft, which used to take a day, now takes a minute.
What it keeps: speed, breadth of exploration, and a much lower cost of trying an idea.
What it risks losing: the thinking that used to happen while making the draft. A designer who sketched twenty variations by hand understood the problem by the twentieth. Choosing from twenty generated variations does not guarantee the same understanding.
The pattern
Read the eras side by side and a pattern shows up:
| Era | Gained | Lost |
|---|---|---|
| Skeuomorphism | Obvious affordances | Honesty, economy |
| Flat (2013) | Clarity, scalability | Signifiers |
| Material (2014) | Hierarchy, shared rules | Distinctiveness |
| Systems and tokens | Consistency, design-to-code link | Per-screen craft |
| Multiplayer | Shared visibility | Private exploration |
| Generative | Cheap drafts | Thinking through making |
Each shift solved a real problem from the previous one and introduced a new blind spot. None of them removed the need to decide what the interface should do for a specific person in a specific situation.
Where human judgment sits now
Judgment has not shrunk. It has moved up the stack.
- Defining the system. Someone decides what the tokens are, which components exist and what they are for. Generative tools are only as good as the system they draw from.
- Choosing among drafts. When drafts are cheap, the scarce skill is evaluation: knowing why option 7 is better than option 3 for an operator on a night shift, and being able to say so.
- Knowing the context. A model does not know that the plant floor is loud, that the security analyst has six monitors, or that the user is filling in a form after a bereavement. Designers who spend time with users do.
- Protecting what the last shift lost. Signifiers, accessibility, honest feedback and restraint keep getting dropped in each transition. Someone has to notice and bring them back.
Each era treated the previous one as naive. The more useful view is that every era was partly right, and the job of a designer now is to keep track of which parts.
Sources
- Apple Unveils iOS 7, Apple Newsroom — 10 June 2013 announcement and Jony Ive quote on simplicity.
- Flat Design: Its Origins, Its Problems, and Why Flat 2.0 Is Better for Users, NN/g — Kate Moran, 2015, on lost signifiers and Flat 2.0.
- When Material Made Its Global Debut, Google Design — retrospective on the 2014 I/O launch, paper metaphor and adoption.
- Atomic Design, Chapter 1, Brad Frost — 2016 framing of design as systems of components.
- Design Tokens Community Group, W3C — the group behind the shared token format.
- Design Tokens Format Module 2025.10 — first stable token specification, 28 October 2025.
- How Figma's multiplayer technology works, Evan Wallace — 2019 explanation of Figma's CRDT-inspired, server-authoritative design.
- Introducing Figma Make, Figma — May 2025 prompt-to-app prototyping tool.