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
7 comments
-
Anonymous
commented
Same issue for me. I have all but given up on states (and maybe XD soon). It frustrating to have a very useful feature so close and yet so far.
-
Jeremy Mcleod
commented
I cannot emphasize enough how terrible the current state of component states is. For example I have what I think of as a relatively simple menu. It has six different sections, and a dropdown where you pick the section. There are states for each section being active (which shows a different list of links and changes the header) and a state for each section with the dropdown open, for a total of 12 states.
You know how long it takes my seriously beefy computer to change between states on an instance of that menu? ONE HUNDRED AND FORTY SECONDS. That's just madness! Not only that, on a full navigational mockup, with 30+ instances of that component, XD will at some point wind up using almost TWENTY GIGABYTES of RAM. Again, that is madness! There is no reason for components to be as performance heavy as they are right now. I know Adobe has a ton of amazing talent; it's time to focus that talent on figuring out how to fix this feature.
-
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.