# A tale of two parameter architectures--and how we unified them

DevFeed: [A tale of two parameter architectures--and how we unified them](<https://devfeed.tech/articles/a-tale-of-two-parameter-architectures-and-how-we-unified-them-9486.md>)

Original publisher: [Read original article](<https://www.figma.com/blog/a-tale-of-two-parameter-architectures/>)

Author: Jenning Chen

Published: 2025-07-29T00:00:00Z

Content type: article

Language: en

Sources: [Figma Blog](<https://devfeed.tech/sources/figma-blog.md>)

Topics: [Figma](<https://devfeed.tech/topics/figma.md>), [Architecture & Design](<https://devfeed.tech/topics/architecture-design.md>), [Scalability](<https://devfeed.tech/topics/scalability.md>)

Tags: [architectures](<https://devfeed.tech/tags/architectures.md>), [figma](<https://devfeed.tech/tags/figma.md>)

## AI overview

Figma unified the previously separate architectures behind variables and component properties into one parameter system. The new foundation removes inconsistent behavior, improves developer velocity, and is intended to scale across Figma products.

## Source excerpt

After launching variables and component properties in quick succession, we were left with two different underlying architectures for parametrization. Here's how we unified them for consistency and scalability.