I have 2 big repeating groups where users can filter elements based on multiple criteria (including strings, but also elements just displayed on the gruoup).
I want to save filters users use on repeating group.
I found an option which saves data in local storage. I am currently working with it but…
Is there another way, more native to bubble in the end?
I’m really not sure why local storage isn’t a native Bubble feature…
But in any case, if you don’t want to use local storage, then save it in the database - that’s a more native Bubble way.
Well don’t know if you would agree with my logic below as I percieve it differently.
Any plugin not created by bubble is not native.
Using any plugin in bubble means you actually use features bubble was not designed fully for.
As the same way we can say linking bubble to xano database and using it instead of native database is a bubble feature. And I wouldn’t call anything that requires api call or plugin a native feature.
What is your perspective on that?
I think you misunderstood me…
I wasn’t saying Local Storage is a native Bubble Feature (it obviously isn’t).
I was saying I can’t understand why Bubble doesn’t have Local Storage as a native feature…
Given that it’s such a fundamental (and simple) part of modern front-end web development, and every other no-code/low-code tool I’ve used has it as built-in functionality.
The same could be said for quite a few things, actually.
Got it! I have misunderstood you.
I agree 100% as usual with you. Let’s push them to have those things or to make saving the filtering status somehow faster - like having an action that can save custom state from the page if it is left in anyway via backend flow.
Bubble is such a brilliant tool, unparalel to any other in case of simplicity and development speed (and required coding knowldge to start), but some functionalities just lack.
