Sorry for the slow reply, Christmas break. Catching up.
@Rawalanche - Yes, that in editor panel is very different from the rest of UE in the sense that it loads a webpage, which is probably the UI performance you are noticing? It needs to load and pull all the thumbnails and so on from web, which takes time. Is that what you meant with performance? Do you experience it to be slower in editor vs in a browser?
We are looking at integrating part of it into the content browser natively for 5.6 or 5.7 we hope. That would see any assets you have access to as part of your a new section of the content browser (even if you haven’t yet downloaded those), but would continue to see the purchasing of assets and browsing of new assets be done via the plugin (and thus web) panel.
That should lead to improvements in terms of handling the content you already own but overall this one is tricky to solve fully. All the asset images and such data on Fab are ultimately on web, so they do need to pulled over which will always take time and be less responsive than if all of it is on disk.
I will discuss with the team whether there are other web performance things we could do to speed up the plugin though.
@ozCROM @Maciek_Leto The roadmap is indeed a bit vague timing wise, but we want to get a significant number of these items at least in progress/partially released before the end of spring. The items on the roadmap are placed roughly in the order that we want to address them in, which is why we are currently working on Search, but we are definitely going to be jumping back and forth a bit here and there too for some of it.
The vagueness is there to help give us some flexibility, because it may be that some items take longer than hoped, or because other work may surface. There are also a number of other things we are working on that have to be done but that aren’t in themselves contributing to making Fab a better experience and are thus not included on the roadmap. For example bugs and issues, additional compliance items, we have some tech debt, work surrounding Quixel entitlement migrations and so forth are things that are coming up as we go along and can cause changes to our sprints.
I understand a precise timeline would be awesome, but we hope the current roadmap provides a reasonable sense of what we are looking at improving and about in what order.