Improved Component State Performance
Component states are awesome, but right now the size increase for a complex component is not scalable. After doing some testing, components appear to increase their size proportionally to the number of states.
For example if I have a Default state, create a new state and move the components, say in a mask, to do an animation the size has now doubled. Then if I copy that to a new artboard, it doubles again, because both states get carried around. Therefore what originally would have been a master with an instance in 2 separate artboards with size 2X is now size 4X because there are two instances with 2 states. Add another unused state and it is now 6X
I understand why this method would be used, but it has not been scalable for some of our work.
Any plans to address this?
Tony M
shared this idea
5 comments
-
SpotOn-Wes
commented
I am currently having the same issue.
Once using States, my file size increased by over 100x!!!!!!!!!Other posts say that this bug was fixed in v18— it was not i'm using v24.4.22
After more than 1.5hrs on the phone with support, the "solve" was to revert to an old version of my file before using States and re-doing all the work I've done since (presumedly not just to the specific file but also to any that have Linked Components from it that use States)
-
SpotOn-Wes
commented
This issue has rendered my UI Kits virtually unusable
-
SpotOn-Wes
commented
Components with States drastically slow XD's performance
Even simple components (eg. an icon) with multiple states have horrendously slow performance.
Simply selecting a Component with multiple states takes upwards of 90 seconds. Moving the Component is also unacceptably slow. Changing the State is similarly slow.
Basically, States make Components super powerful. But, they also render my files un-workably slow.
-
Tony M
commented
Awesome. Thank you!
Is there a place where I can track progress?
-
Daniel Wabyick
commented
Thank you for taking the time to investigate and posting. We are already actively working on this issue - as we know this can impact heavier usages of components and states.