Hi team, this follows the launch of UI3.
We use a design system, and one thing our team found was incredibly slow performance of the component search (Shift I).From less than a second to minutes.
This was related to UI3 only, as we could switch between UI2 and UI3, and where UI2 would take less than a second to return relevant results, UI3 would just show “loading” placeholders for minutes at a time in the same file. I was thinking yesterday I should take a video, only to be locked into UI3 today. Our team would regularly check UI3 every few weeks, as this would happen across devices, on web, and in the app.
This is literally 100x worse performance (from less than a second to minutes). It’s like UI3 does not have a debounce, or the search is trying to do other things at the same time like identify how may of those components are in the file (great to know, but way less useful than a fast search).
I have seen numerous other threads on this, and I was just wondering if there was any updates? This has slowed our design process to a crawl.
Many thanks,
Isaac @ RIVER
