Good morning!
So I have a general (possibly silly) question for anyone who's built large or complex Experience Builder apps.
The project I'm working involves slightly over 20 different maps - the maps are all similar and contain the same layers, except each one has been pre-filtered to show the specific information we want to show for that page (like 20+ pre-configured map views so the users don't have to dig through 20+ layer selections themselves).
I posted a couple of questions last week regarding some issues I was having with some of the layers in the maps - they would not draw properly, or it seemed as if Exp. Builder was having issues connecting to the right layer in the right map.
So, it occurred to me - and here's where I'd like to hear from any past experience anyone might have - that connecting 20+ maps as data sources and having as many section/views (aside from landing, methodology, and 'help' pages) in one single app is maybe pushing Exp. Builder a bit too far (there's been a few 'out of memory' crashes as well).
Would it be better if I created 5 separate Exp. Builder Apps (one for each of the map themes the 20+ maps are organized by) and just embedded those into the larger one (with the landing, help, methodology, etc.)? I assume it'd be more memory-efficient to just call separate apps than to load everything into one, but is it also stable?
Thanks!
