Redesigned property editor beta: Now available to everyone

Hi everyone,

I’m Lindsay, a product manager at Bubble. Since the redesigned property editor beta phase 1 launched in December, we’ve been listening to your feedback and shipping fixes and improvements along the way.

Today, we’re opening the beta to all users, and we’d love to hear your thoughts. You can switch to the new experience using the toggle at the top of the editor, and toggle it back off to go back to the old one anytime.

How your feedback shaped this update

We launched the redesigned property editor in December with the intention of building it in public and improving it along the way. The community was quick to flag issues. You really showed up with your feedback, and we’ve spent the last few months working through it, with our latest update released in April.

At a high level, we focused on three areas:

  • Removing popovers to reduce clicks
  • Redesigning the dynamic data insertion to feel smoother and less finicky
  • Improving the overall visual clarity of the editor so it’s easier to scan and read

What we’re excited about

Beyond the fixes, there are so many improvements that our community contributed to, and we’re genuinely excited for all users to get access to them:

  • Drag-and-drop reordering for conditionals, constraints, workflow fields, custom states, and more
  • See the count of workflows, conditionals, and custom states on each element
  • Expandable dynamic expressions into a larger popover when you need more space
  • Auto-focus in more places, like creating constraints or setting fields and custom states in the workflow tab
  • View and edit workflow events and actions from the design tab without switching tabs
  • Searchable color picker to quickly find color variables

PE-conditionals 1000x1000

Try it and let us know what you think

Toggle it on whenever you’re ready. We’ve been using it internally for a while now and have benefited from the improvements, and we think you’ll feel the same.

We’re excited for more of the community to get access but we also recognize that switching to a new UI mid-project isn’t easy. The migration guide is the best place to see what’s changed and where things have moved, with our documentation covering everything in more detail, if you decide to toggle it on.

This is still in beta and your feedback continues to shape the final product. We’ll keep monitoring what you share here and making changes accordingly. If you have specific feedback, you can submit it via the feedback link in the toggle, or in Settings > Versions > Beta Features > Property editor redesign.

We appreciate the time and care this community has put into helping us get the property editor to this point. Looking forward to hearing what you think!

— Lindsay

As a long-time Bubble user, it’s a big transition and an uncomfortable one with something I am so used to. But I really have to say I appreciate how much @lindsay.esterman and the product team have been listening to our feedback and thoughtfully rolling it out. I’m excited to keep the feedback coming and keep improving it.

As a beta user, I used this a lot and it has been great. It’s an adjustment for sure, but if you already know Bubble, you know what to look for. I keep it on all the time when I’m building and now am uncomfortable when having to work back on the old version. This is a great update. Hope to get all the bugs out now that more users can use it. Good job you guys! :blush:

Has anyone seen any editor memory improvement with the new editor? The slow drain and lag is starting to eat at my soul day after day.

This is amazing news however! :star_struck:

Really nice to try it!

I really believe that states should have it’s own tab instead of an icon and popup

Also, hide sections that doesn’t have any setting in it instead of showing it empty.

Congrats on the progress!! Really big milestone :clap: :clap: :clap: :clap:

just a big WOW

Great job

May be some time to adapt but it looks nice

Is there an ETA for when this will be forced onto everyone?

Seems good.

This was done for the new AI Builder?

I do wish a VH height setting would have been added. Yes, I know there are other ways to set it, but a simple click would be helpful. Also, a simple click to reverse columns on mobile :grinning_face:

I just hope you don’t enforce it on us before I finish my app (hoping to finish by mid June). It slows me down sooooo much, I honestly think it’s a terrible backward step. Sorry but our memories have been trained and this new editor is just… well… awkward.

The property editor seems more like the Elementor Builder for WordPress or somewhat Figma, and less like Bubble as we know it. I’ve used both, so not much of a problem, but the editor’s openness of bubble is way better than others, just don’t congest features/options from singular to groups

For example, one of my button elements had a 20 px top margin made previously. I opted for the new editor a few hours ago. And to change the margin of the button, it took me nearly 15 mins to find the option to change (I thought the option was missing). I can see the margin, but can’t find the option.

I agree with other devs above, it doesn’t feel as snappy as the regular editor, hopefully it will get faster and simpler to use as bubble already is.

I think overall is good but some bugs are annoying right now:
Clicking add, cuts the conditional, I can’t see what I’m adding to expression.


Another thing is margin, sometimes show as a string called 'Mixed’instead of a int like ‘10’.

It’s my first time trying it (was not part of the initial beta), and I will have more feedback to provide; but I must immediately point out what I consider to be a regression (or glaring omission).

In the old expression editor, hovering a parenthetical “block” (for lack of a better term) would highlight that block and dim the rest of the expression…

However, the new expression editor has no equivalent visual feedback…

This feature is roughly the equivalent of highlighting a block of code (or connecting the opening and closing curly braces with a vertical line) in a code-editing IDE, and I found it very helpful b/c it eliminates the need to constantly mentally parse the expression to determine where you might want to insert a new subexpression. It was thoughtfully added by the engineers who implemented the original parentheses feature, and I’d love to have it back!

What I propose is using a background highlight similar to the following…

Or if that’s not feasible, at the very least make the opening and closing parentheses of the hovered block stand out, like bold and bright magenta or something - not just some subtle color change.

Thanks for considering!

Isn’t this supposed to underline now @lindsay.esterman or was i imagining that

I agree and just wanted to boost this request with a dedicated reply. It’s time to stop treating custom states like the Rodney Dangerfield of features and give them the respect they deserve.

(Don’t worry witto custom states. I still wuv you.)

:smirking_face:

@randomanon this is the evidence you’ve been hunting for, video is in original post

Where’s the dark mode? My eyes will thank you.

I have tried a few times to use it in Beta at different stages and on different apps but have found so littered with bugs to make it basically unusable (not to mention the sidebar hiding / showing all the time). I dread the moment when this will be forced on me…