As a designer, I'm working on a large-scale Figma project with over 3 years of development. The file includes numerous deeply nested components used throughout the product.
Even minor changes to a single component—such as swapping a fill for a stroke on a button—trigger severe performance problems:
- Figma freezes for 5–10 minutes as changes propagate across all instances.
- Another 5–7 minutes are needed to sync with the server.
- The tool becomes sluggish, with 1–3 second lag on every action due to background updates.
This makes efficient work nearly impossible. I can't make consecutive changes without waiting for updates after each one, significantly hampering my workflow.
Proposal:
Implement a feature that allows users to temporarily freeze a component, preventing changes to the parent component from immediately affecting its instances.
Implementation concept:
- Enable a "freeze" mode for the component.
- Make multiple edits without triggering updates to child instances.
- When finished, unfreeze the component to apply all changes simultaneously.
This enhancement would significantly improve performance for large design systems and make Figma more effective for enterprise-scale, long-term projects.
!-->
