Yeah, objects (the lack thereof) are kind of holding us back from many things – like supporting “offline mode” as another poster mentioned (but much else as well). If Bubble did have “in memory” objects, one could actually build a plugin to implement IndexedDB via Lexie and that “front end” database could be essentially a clone of the backend database. It’s wild how similar those architectures are.
@gazinhio, I’m not quite sure what you mean by “variables in backend workflows”? In my List Popper and Friends plugin, there are a couple of (VERY simple) SSAs that simply forward an evaluated expression to their outputs (Flow State and Flow State List) and so they can serve exactly this purpose. I know it would make more sense if there were a native action for that (and also if we could build a similar plugin for the client-side, which we cannot today because the client-side actions API does not return values to the workflow)… but it does exist today. (Granted, there is cold-start time for SSAs.)