The Washington Post’s inclusive process for creating new design system components bridges the gap between design and development.

Our nine month journey to horizontally shard Figma’s Postgres stack, and the key to unlocking (nearly) infinite scalability.

When our permissions system broke at the seams, everything came to a halt. This is the story of how we fixed it.

Large prototypes took minutes to load, and users took notice. Here’s how we overhauled our prototype player to improve load time and stability.

Shishir Mehrotra shares tips for harnessing the power of the braintrust, asking the right questions, and landing a moonshot.

Design Manager Juli Sombat sheds light on how a need for more cohesion led Spotify’s design systems team to approach components in a new way.

The best teams understand what they’re producing, why they’re doing it, and how they can get it done—here's how manager's can make it happen.

How the Figma infrastructure team reduced potential instability by scaling to multiple databases.

Software Engineer Dorothy Chen explains the technical challenges and opportunities in making Figma keyboard shortcuts more accessible for everyone.

Data is a vital component in how we improve Figma day by day. Learn more about what kind of data we use and how we use it.

The physics behind spring animations.

A peek into the homegrown solution we built as the first design tool with live collaborative editing.

One of the problems we had to solve when we added multiplayer editing to Figma was supporting simultaneous editing of ordered sequences of objects.

The technical challenges of updating our autosave system.

A look at how we identify and address bugs.

How Mozilla’s new language dramatically improved our server-side performance.