Our teams are facing performance issues in Figma while using design system components. They constantly have warning and error messages related to memory usage.
This is happening mainly when we use components:
- with several variations and properties
- composed of other complex pattern components
Examples of components that are facing this problem:
- Table
- ChatBubble
- Pagination
- Nav
- And more…
We already investigated Figma’s documentation here about this topic and we understand that we’re developing the components in the correct way following all the best practices mentioned.
The only solution that we see is breaking current components into multiple ones. For example, break the component into smaller components like ButtonPrimary, ButtonSecondary, ButtonError… However, this is not a complete solution and doesn’t seems right/the best approach for us since we have great features in Figma like boolean properties and more.
- Do you believe this is a best practice for the construction of complex components and patterns in Figma?
- Do you have tips about the best structure for this type of complex component that avoid the memory usage problem?
- Do you have suggestions on how we can improve our library to avoid these issues?