Experience Builder or ArcGIS Hub for improved performance

[ckellow]

Hello, 

I have created an Experience Builder within ArcGIS Online and the performance is very bad. The Experience Builder is built following an old structure of web applications my company would make. This structure used web app builder's embedded into a Story Book (tab based structure). I have tried to mimic that within ExB, but the performance is very bad. Currently the ExB has around 30-35 web maps hosted in, with around 10 current pages (some with sections/views), and then all have many widgets configured similarly to the way Web App Builder was able to link together. 

The reason why all of those maps are needed is because many are very different and cannot be configured with lists/filters because the information within the map is very different. Also, some maps are used with the same feature layer, but with a different symbology which cannot be configured within a widget to change the symbology of one web map used. 

My question comes to this, if the performance of ExB is very slow and is caused by the overwhelming amount of web maps, would performance be better to use ArcGIS Hub as the structure with embedding standalone ExB into the Hub? Or can performance of the ExB be improved by using embedded links to standalone ExB to get around the web maps all within one ExB? 

Thanks, Cole

[JeffreyThompson2]

Yes, breaking things out so you are not loading so much stuff in a single Experience Builder project should improve performance. Either making a Hub site or putting links inside an Experience Builder project should be effective. Which one would be better? I don't know for sure. I suspect the Hub site as it is specifically designed for that purpose, while Experience Builder comes packaged with a lot of other things.

[TimWestern]

I wonder if your use case is a good case to have a switchboard of dashboards that then load one of several selection experience builders.

(To Clarify what I'm suggesting, if you have so many diverse maps and experiences, instead of trying to create one Experience to rule it all. Create Multiple Experiences for subsets of the needs, and use a Dashboard to route people to the right groups of experiences.)