Property editor redesign (beta) is here!

Another swing and a miss. I am guessing someone in product leadership likes Elementor!

I mean c’mon, what in the blue heck is this:

The good:

  • nice to see colours when there’s an issue that needs to be dealt with
  • custom state views/details are better

To improve:

  • far too washed out
  • fonts/sections are too small
  • expression composition is FAR AND AWAY the most important thing and it much easier to create in the old version.
  • ‘workflows’ tab should be added to the header where visual, interaction etc are, especially since the ‘edit workflow’ button is gone which I guarantee 100% of power bubble builders use hundreds of times a day

I think I’m beyond the point of praising intention and effort. Feels bad saying this, but there is a definite product leadership problem at Bubble…and probably really bad technical debt. Perhaps it’s time to split the platform and pull an ‘active campaign’. For those who didn’t know, Postmark is owned by Active Campaign. Instead of duct-taping the platform together, they left the core product (AC) for enterprises and spun up a new company/platform for Postmark. I think we can all agree Postmark absolutely rules.

Maybe the existing platform needs to have a ‘legacy’ label slapped on it for those of us with really big, complicated sites and use the new AI builder on ‘bubble lite’ as it seems obvious these updates are targeted at new customer acquisition.

I agree. While they’re at it, if they want to add an “Add All States” as well when setting a state of an element I may reconsider switching to this new editor.

Thank you all the feedback - we are definitely watching this thread, and will use this to improve the new Property Editor.

I might’ve missed something - I don’t see this in my BETA. I’m late to the game, it seems.. lol

Here’s my honest feedback. I created an app from scratch, without using AI. Completely blank. And at this first stage, I’ll just check the properties directly on the page.

I’ll review other elements in the coming days, but for now let’s start with the new properties editor container.

PROPERTY CONTAINER

1 - I know you’re adopting a cleaner layout, with practically everything based on the color white. But a slight background color on the properties tab would help users easily identify where the input fields are.



VISUAL TAB

2 - In the previous version we just need to click one time in the inputs to set the min width/height. Now we need to click in the “+” icon, select these properties to add in the tab, then click in the input. So 3 clicks for each property instead 1.


3 - Now if you set any value to the Builder width and then change the Layout mode, the value is automatically set as 1079.99, why that?


4 - Why these tooltips are not consistent? Sometimes they appear just when you click in some inputs in the given section, other times not.


5 - In the previous version, the layout was the first property in the “Layout” tab, so switching between properties would display or collapse other properties, but there was no problem. Now, this property has been added to the first tab “Visual”, and after Size. Switching between row/column/align to fixed affects the display of the higher properties and requires the user to move the mouse to switch between layouts again. It’s not the end of the world, but it requires more movements.


6 - When trying to edit a Style, the shortcut take us to the color variables.


7 - One of my screens is widescreen, and I work with two split screens. When I do this, the properties tab in the styles gets cut off.


8 - The new color picker is nice. But there are some bugs.

  • Hover over color variables does not display the variable name.

  • When expanding the variable section it moves the color picker down and also expands the container outside of the editor.


  • Once expanded, if it is collapsed, it remains with a broken layout.

  • Once opened, the color picker can only be closed if we click the close icon. It should close automatically whenever we click outside or even on other properties.

  • The shortcut for creating new color variables is very handy, but since we’re on the subject, it would be great if we could reorder the variables in any order we want.


CONDITIONAL TAB

9 - I liked the new ability to reorder conditionals by dragging and dropping, but I think the area that enables dragging and dropping should be limited to a specific location. Currently, any area of ​​the conditional allows this to be done, and I think that in some cases users will accidentally drag things (especially when the editor is a bit slow/freezing), and this will cause problems.

Also liked that now strings have a different color. But when dealing with expressions at the end of the container, the options dropdown cuts off those with large labels.


10 - In some cases, after set up conditionals to a style and apply the style to the element, the conditionals tab in the element or the entire property editor is not rendered, even if we refresh the page, the conditional tab will fail to load.

This was a quick analysis of the page, without even testing it with other components. But I will do that in the coming days because, honestly, in its current state, I see the negative impact this will have on my productivity. Not because I have to relearn where some things are and how the new editor works, but because of the obvious issues in this beta version.

I don’t think it’s been released to all users yet, but you can try disabling any ad blocker you’re using.

Thanks – Honestly I wish I had an adblocker.. Youtube’s been killin me lately. I’ll sit back and wait!

Btw, taking advantage of all this restructuring, why not add some missing CSS properties?

Some basic ones would be:

  • flex-wrap: nowrap
  • flex-direction: column-reverse / row-reverse
  • backdrop-filter
  • clip-path
  • mask-image
  • overflow-x
  • clamp
  • hyphens
  • line-clamp
  • user-select

In addition to dynamic units: vw, vh, vmin, vmax, dvh, em, rem.

And finally, dynamic fields, especially in component dimensions. This would reduce the use of many plugins and custom code.

Another thing that would help a lot would be a property to add CSS classes. I know we have plugins, but why not have this natively? It would be almost the same approach as adding IDs that already exists natively, but classes would be a great help for conditional and reusable customization.

All these additions would allow improvements in many aspects and would also be used by Bubble’s AI.

Correct this is only released to 25% of users, and people can opt-out. Given how sensitive this is to our users’ productivity, we’re not rushing here

I know for a fact this isn’t accurate. You can’t trust this number all the time, for some reason.

As Emmanuel said, we appreciate this feedback and the team is actively monitoring the thread. We’ll continue to improve the new Property Editor while it’s in this limited opt-out Beta before rolling it out to all users

really difficult to believe bubble team internally used the current state of the new editor and decided it was ready to be “beta” tested.

common guys, all the Ai stuff going around and you push this type of updates. youre gonna loose your advantage, and youre making it harder and harder to justify using bubble to clients as an agency.

lots of extra clicks, the readability of the new expression composer is terrible, and there are random color feedback, some of my expressions are highlighted red , but are correct.

Can you and Josh just go back to designing everything yourselves? Just make a crappy sketch and let the “designer” make it look nice, don’t let them architect the actual functionality unless they’ve built a substantial Bubble app from scratch.

@emmanuel Can you tell your designers if something is used frequently (such as expressions or width settings), make it directly visible and easily accessible? If it’s used infrequently, it doesn’t need to be. In that case a couple of clicks do not matter.

Baptism by fire for you Brian :joy:

It feels like the interface became much brighter overall. Previously, the contrast helped visually separate elements and made the editor easier to work with.

Now, everything tends to stack vertically, and feels like what used to take just a few clicks now require noticeably more steps. I also really appreciated the ability to freely drag the editor around the screen.

The new custom states view is a good improvement. The ability to drag and drop custom states and conditionals, as well as to name conditionals, is also a positive change.

So, after using the new editor all of yesterday and a majority of this morning, I’d like to share something with the Bubble team. Bugs are given, this is a very restricted Beta and so issues here and there are fine, seems like the team is replying to most of the bug report comments.

However, me and my team are watching this redesign very carefully because the past year and a half of Bubble newsletters have focused on so many AI-centric initiatives and buzzwords. Forget the promised conditional and looping workflow features, or the fact that main API integration is a Plugin with extremely limited functionality (which is nuts to see in 2025). The actual “redesign” of the editor makes it look like we, as paying users, are not even a focus of the company anymore.

  • How did the conditional text fields and dynamic data syntax get worse in this new iteration?
  • Why are plugin descriptions overlapping fields and the conditionals within those plugins giving random syntax errors?
  • How come any field in the entire editor that has text / dynamic data shows about 8 characters before becoming “…” even though the old editor had them on new lines, allowing easy glancing to see values (less clicks).

Once again, bugs are a given in a beta, but these things wouldn’t make it past round 1 of QA / initial feedback. Our team doesn’t want to jump ship to another platform, but we don’t about Bubble’s forced focus on AI; this redesign is for all Bubble developers, and we will be watching closely to see how you guys respond to feedback.

They have shifted focus from “power users” to “new users.” However, they have no idea what is needed to attract “new users.” I outline this here:

Everything has been said. I switch after one hour. No doubt this redesign is needed for future features, but the idea board is full of improvments we asked for years now and nothing shows up.

Take the API connector as an example… all apps need to be connected to external services. And still a plugin, no ability to add notes(doc), its own tab etc etc etc

Hope the new team that we talked about at the Bubble tour will shows up soon @emmanuel because we are very frustrated to see things not requested come and requested features never come :melting_face:

Seriously,take the most upvoted features : they are there since not months but YEARS : 2020, 2021, 2022.

Ideaboard doesn’t capture beginner needs or power user needs. Only people in the middle or very macro stuff like page load speed,servers, privacy rules, mobile native, darkmode.

I see posts like these all the time from beginners “I use bubble file uploader, it is probably my fault but…”. To capture these they need better feedback system.