I need to work on the UI, but this is a general idea.
I haven’t ever built a plugin on Bubble…if anyone else wants to run with it, I think it would be a great idea.
What are your thoughts on this?
Added: Sorry, I uploaded the wrong image. This image was from an earlier prototype. Here is the correct image where you can pick the custom state type:
Added Again: If anyone thinks this plugin would be useful, I also have another couple of plugins I think could revolutionize the way users build with Bubble.
Anyway, just interested in your thoughts on this, if I should proceed or call it a day on this one
There is a potential update coming to “improv(e) visibility for custom states” so it might be worth waiting to see how that update could change things.
Color me intrigued! I’m curious if you’re actually created native Bubble ‘Custom States’ or if you’re creating states on the plugin that are exposed? Reading your original description I thought you were referring to a tool on the editor making it easier to manage states - but with the screenshot I realized it was on the web / app side.
One interesting use-case that would be less about creating states, and more about managing them (especially if you were able to identify current custom states) is not only listing the states, the elements they’re tied to, and current state of each - but effectively it becoming a ‘switchboard’ where an admin could toggle data to test…
That sounds good, not gonna lie, we are waiting this for ages! If we could also organize into folders and be able to search for them. What about a object variable as well? Also dynamic data types in popups insted of static ones..
I’ll do a little more work on it, and also wait to see what Bubble puts out.
I always thought at the very least, if you put a custom state on an element, it should change the color of the element name in the element tree. Like maybe red or something. Then, if you expanded the tree, you could easily tell where the custom states were
Yeah, we’ve requested something like this many times. A better, easier, and faster way to visually identify all custom states on a page/reusable element. The same goes for comments/notes.
Also, some way to create global custom states would be amazing. This would allow us to create a lot of new functionalities, like native communication between elements, especially those within REs, without the need for custom code, URL parameters, or workarounds like nested Custom Events acting as external triggers.
These global custom states would allow us to create a central control (maybe a reusable element or something similar) that would help us improve best practices, especially in reusability, maintainability and documentation.