Having a way to quickly identity elements that are overlapping, for example by showing their borders in red when a button is held down or a setting activated.
On big SPA’s, two out of 100 groups overlapping by a single pixel can wreak havoc. Would be a timesaver to be able to spot them quickly
Reading through, lots of great ideas here…Bubble dreams
I have a few ideas scattered together in this thread here that I think could be of some use to others as well:
But I’d really like to see the ability to add comments on a condition basis. So on a element that has many conditions, we can add a specific comment to the condition (not the whole element) with regards to its functionality. Granted its quite a niche request, but I’ve found a few times using a series of complex conditions and coming back to it, being puzzled. Commenting on the element works, but bit cumbersome, especially if the order changes.
Bubble based editor zoom hotkeys! Trying to get the right zoom percentage in the grid list is repetitive. Check Figma’s functionality for how easy it is to zoom in an out with a scroller
Suggestion: Ability to “show” hidden elements in the editor by default - Even if they are not visible on page load.
We all know that hiding an element then showing when you need to is a great performance gain for your Bubble app - But it makes things clunky when you’re using the editor. Each time you load a page to edit that has hidden elements on page load, the element is invisible - Leading to large blank spaces on your editor page - Requiring you to manually un-hide each time.
For SPA apps, it’s a killer if you have 25 hidden groups on a page.
AFTER (put an overlay on top of hidden elements, so when you open up a new page, you can SEE what all hidden elements you have without having to click into each one):
This idea was brought to you by a co-worker who was tired of working on MVPs with me and going to pages with 10 hidden elements (for maximum performance) and wondering where the heck they needed to make changes!
I completely agree!
If I can add my two cents, I often use overlay and collapsing groups in the same SPA. Having all hiddens to be visible would mean hiding a bunch of elements on editor load…
I suggest that the last visibility state should be used instead, so when I do an editor page refresh, we would find the displaying in the same state than before.
By the way congrats on the clear “fake-screenshots”!
Not sure if someone suggested, but it would be awesome to have the ability to duplicate one data entry (this is cool when you need to test RG with more data instead of creating one by one).
Time to whip out the Jira backlog and start prioritizing I actually saw on spotify’s product board they allow users to vote on epics to help suggest prioritizing improvements.
Hi! So this is something I posted about on the forum, but would be great to implement. From a design perspective, setting up grids/gutters/margins are important for best design practice. Right now Margins are not able to be set so the left one is always 12px. Can we implement something to change the default margin for that left column?
I don’t know if this has been mentioned before, but if you’re like me, “:defaulting to” is so useful for dealing with empty text values. Maybe having it for dates, or even numbers would often be useful as well.
Yea, 56 is the biggest one for me productivity wise. I deal with many pages on my apps - So to go from one page to another w/ many hidden elements, I spend too much clicking un-hide and “show all children”.
“Show all children” <- Honestly forgot about this option and/or was overlooking it, so thanks @w.fly for mentioning it . Screenshotted below for fellow n00bs like me
Also another update – Bubble support replied to my bug report on this and stated : “Regarding the element tree and the user interface in general, we are hard at work totally revamping the Bubble editor. The new version should be launched in beta by the end of the year.”