“Loading” happens in two stages:
-Sending the code for the elements (ie, basically everything you fill out in the property panel in the editor). Yes, we do need to send the code for popups on page load.
-Executing any queries that fetch dynamic data. Ie, when you do a search, actually performing that search. Here, we don’t do this until the popup becomes visible.
Thanks to everyone helping debug www.pflegetiger.de. Re:
Yeah, it’s part of the core Bubble framework. It’s not going to go to zero any time soon, but it’s definitely shrinkable. We periodically audit the size of the code we’re sending over and cut unnecessary things to keep the size down; we’re probably overdue for another audit (the last one was over a year ago I think!), so I’ve added that to our project list, though no promises on the timing.
I’m talking off the top of my head, so no promises that this is correct, but what I think is going on is that right now to display the list of inventory things, we have to load all 300 items, whereas to do the search, we just need to load enough items to fill the repeating groups cells that are currently visible. We’re working on a project to optimize this (as part of an overhaul of our database query planning engine). Another factor is that we have to load each of the 300 items one-by-one, whereas the search we do as a single database query: we aren’t working on this right now, but it’s on our backlog of projects.