timesgasil.blogg.se

Figma blog
Figma blog











figma blog
  1. #Figma blog update
  2. #Figma blog code
figma blog

Join us as a beta tester, tell us what you like, what you don’t, and what you want to see next (sign up here!).Īnd we’re just getting started 😉. We just updated the beta version of our Storybook to Figma feature, and we need your feedback to continue perfecting it.

#Figma blog update

They’ll be able to discuss changes with their developers or update their designs using the revised components.įrom Storybook to Figma in a single click! 👉Sign up here for early access👈

#Figma blog code

This also means that in the not-so-distant future, designers will be notified when a component’s code changes in a way that affects their designs. This will enable them to see exactly what their users will see as they’re designing. They can import an individual component’s story (aka the component and all of its variants), or an entire Storybook library in a single click. Now, we’re allowing designers to bring their live code components - along with all of the variants that exist into code - into their existing design tools via Storybook (starting with Figma :)). The solution: creating a single source of truthĪt Anima, we’re working on creating a single source of truth between designers and developers. This wastes precious time for both designers and developers, and results in inferior products that take longer to produce. Or worse yet, they’re building the components from scratch, either because similar components don’t exist in the codebase or because there are too many components to sift through. Developers are using their code libraries to reproduce designs as efficiently as possible, but the components don’t look the same. The problem: design and development are not in syncĭesigners are using their Figma libraries, which are isolated from their developers’ code libraries. The result is messy code and designs that don’t match the final product. This frustrates both designers and developers, who waste time rebuilding instead of reusing components and their variants.

figma blog

But more often than not, those libraries either don’t match or aren’t updated with the equivalent code components their developers use. Designers build libraries in their design tools (e.g. TL DR - Designers and developers don’t have a single source of truth. Bring code components from Storybook into Figma with Anima > Get early access













Figma blog