Google's Material 3 Expressive restructured tokens around motion and personalisation, not just colour and spacing. It signals where bigger design systems are heading next.
Google's Material 3 Expressive, announced at I/O 2025, restructured how design tokens handle motion, colour dynamics and personalisation — moving beyond static colour and spacing values into more expressive, context-aware variables. It's a genuine shift in how design-systems teams think about tokens, not just a visual refresh. If the system you reference in interviews still treats tokens as fixed values, this is the direction larger systems are moving. You don't need to migrate anything tomorrow, but understanding the token model helps when a design-systems interview asks how you'd structure scalable variables in Figma or Penpot libraries.
Coach
Audit one component in your current Figma or Penpot library against Material 3's token structure and note one gap.
Figma's May 2026 release notes show design systems and code getting wired together through MCP servers and agent 'skills' — Uber's team demoed using MCP skills to keep production code in sync with design tokens.
youtube.com ·
Adoption
Design tokens are now the default, not a bonus
Design tokens have quietly become the default way design systems hand off to code, not an advanced extra. Figma Variables and Penpot's token support both reflect this shift.
designsystems.news ·
Established
Accessibility law is now a design-system requirement
2025 trend round-ups flag accessibility as a legal requirement rather than a nice-to-have, driven by rules like the European Accessibility Act. For design systems, that means baking it into components and tokens, not patching it on later.