---
title: Idea: store motion as springs in your design system
date: 2026-11-11
edition: 2026-11-11
rubric: Tool-stack and workflow ideas
perex: Motion is becoming part of the design system: motion tokens, vectors ready to animate, and now springs you can save. Worth having one source of truth for animation.
topics: [motion, design-systemy]
---

One direction keeps recurring: Figma Console MCP 1.46 added motion token tools, agent-generated vectors have clean layers ready to animate with Figma Motion, and on 10 Nov springs became saveable to a design system.

## What's new / How it works

Instead of hand-tuned easings, define a small set of springs (for example subtle, standard, expressive) with mass, stiffness and damping and save them to your design system.

## Why it matters

iOS and Android development work with springs directly, so you avoid debating curve conversions. Consistent motion improves product feel and speeds up reviews. How exactly each framework adopts the values is not verified; test it with a prototype.

## How to start

1. Pick the three most common animations in your product (button, modal, list).
2. Set a spring for each and save it to the library.
3. Name them by intent, not by values.
4. Hand the values to developers and compare on a device.

## Sources

- [Figma release notes](https://www.figma.com/release-notes/)
- [Figma Console MCP – releases](https://github.com/southleft/figma-console-mcp/releases)