Is the live version on the client side also going to be on SolidJS?
To be honest, I don’t really care about the editor’s UX/UI; what matters to me is that it’s smooth and reactive, on the level of SolidJS. I also hope the user’s side gets compiled.
Right now, it’s becoming difficult to build smth on Bubble. Once you’ve worked with reactive frameworks, the FPS difference is very noticeable. Bubble feels like something from 2010.
I’ve already shared this via the feedback form, but posting here so other plugin devs are aware (and in case they also want to share via the form):
’Information’ fields in plugins are overlapping with other fields in the new properties editor.
New editor
Old editor
This is happening with all plugins as far as I can see.
Hi Bubble team.
Thank you for keeping the option to turn off the beta feature. I truly hope this stays in beta and that you won’t force us to use the new design.
When viewing the app in live mode, you now are unable to see what workflows do…so while debugging you need to swap into dev mode or have a dev mode app open while you investigate live mode data. This is extremely tedious.
There is no way to even know what your workflow is changing or what element is associated with changes.
I want to acknowledge upfront that many of you haven’t felt heard by Bubble in the past, particularly around editor changes. That context matters, and it’s something we’re actively working to improve.
The Property Editor will continue to evolve based on real usage and feedback. For that feedback to meaningfully influence what we build and prioritize, it needs to be submitted through the form we shared so it can be reviewed, tracked, and acted on systematically.
I’ll post bi-weekly updates in this forum outlining:
-
what’s gone live (bugs and enhancements),
-
what we’re actively working on,
-
and what we’re evaluating next.
This is the primary way we’ll close the loop and communicate progress. If you want your input to directly shape the editor, please submit it through the form and look for updates here.
Which form? The one that requires a Google sign in?
And why can’t you use an LLM to parse the feedback in this topic and act on it systematically?
TLDR: forum discussions are valuable for context, but the form is how feedback gets systematically reviewed and acted on.
Yes , it’s the feedback form linked in the announcement. The Google sign-in is there to help us reduce spam and duplicates and to follow up when clarification is needed. That said, we’re aware it’s not ideal for everyone and are looking at ways to lower that friction.
On using an LLM to parse forum feedback: we do read and consider what’s shared here, and threads like this are useful for discussion and pattern-spotting. The form exists so feedback lands in a structured way we can reliably triage, track, and tie back to specific changes over time. That level of accountability is hard to guarantee from long forum threads alone.
Now I am totally confused with Emmanuel writing that the feedback from this thread is being watched and will be used to improve the property editor and Mike saying that the whole feedback should be only submitted using the Google Form. Is it because the whole feedback is generally negative?
The Add/Edit Workflow is probably one of the most important buttons on the entire properties tab, yet it has been hidden.
As Emmanuel and I said, feedback here is being reviewed and important as pattern-spotting and for discussion. The form gives the team structured feedback that is more effective to triage, track and tie back to changes over time. Long form threads make that more difficult to do.
I feel like this topic is a perfect encapsulation of how much Bubble cares about feedback and its users.
I was initially invited to be an alpha tester of the new property editor at the start of November. That Slack channel has been full of feedback about why the new property editor is not ready to be released even in Beta. Everyone pointing to the same issues:
- Increase in the number of clicks needed to get things done,
- Options and menus being collapsed/hidden by default
- Important buttons being reduced in size, hidden
- Etc etc etc.
The theme was pretty clear - the new property editor has terrible UX. Essentially none of the highlighted issues have been fixed.
The Bubble team still went ahead with a Beta release. Apparently to gather more data. As if the feedback from alpha users wasn’t enough. But whatever.
After the initial post, OP has just disappeared. So much for a feature that is “sensitive to user’s productivity”.
How many times do the same pieces of feedback need to be submitted for the Bubble team to see that pattern? And in how many different mediums (Slack channels, DMs, forums, forms) for Bubble to finally hear - this UX is terrible for productivity. Why can’t someone in the Bubble team categorise and file feedback from the forum in their spreadsheet? Hell, an LLM can do it for them.
How come Xano, WeWeb, Lovable, Cursor all get this right, but not Bubble? Why is it that every time the Bubble community is pointing out how something can be improved the response is always “we are looking into it”, but it never gets done?
@emmanuel @josh I’ve reported this in the past (directly to Emmanuel after Bubble chose to go into beta for the new expression composer that was released, and I was part of the Alpha tester who said it was not ready at all!). Pretty sure it was the same with the new workflow layout, and now it’s happening AGAIN with the new property editor. WHY? Or why do you have ALPHA testers if this is not to listen to them? (and since I’ve reported this, I’ve not been part of any new alpha testing… maybe it’s related?)But I’m happy to not be part of Alpha tester when I see that Bubble continues to not listen to them!
If you don’t agree with the changes as they are, then there’s no point in agreeing. 
Does anyone know if it possible to switch the Styles section to the old editor mode as well?
I have some buttons that have an image at the top structure and I don’t know if the configuration was available in the old styles editor or not. I noticed now it is not possible to configure icon placement on a button in styles (left right top etc.), but honestly I don’t know if this was ever the case 
What Bubble should do (but probably won’t)
Make the editor versioned
Power users need the ability to pin editor versions they trust and opt in to new ones on their own terms.
Open-source the editor (the dream)
Keep the runtime, compiler, and hosting closed. Open the editor itself so the community can improve UX, performance, and power-user workflows, and add real extensibility. Think the n8n model; it works for a reason.
Add a proper Dev Mode
JetBrains figured this out years ago. Figma followed with Dev Mode. Bubble hasn’t. Split the experience: a beginner mode with guidance and guardrails, and a builder mode that’s fast, dense, and unapologetically ugly if needed.
These are just some food for thought, and they’re undeniably big changes. But what many of us keep asking for; small, incremental improvements; either never see the light of day or ship half-baked. The core issue isn’t individual features I believe, it’s more about how Bubble is operating. I would love to keep editing this with anymore ideas people have.
I previously extended an offer to @mike.alvarez to summarize/structure the feedback in this forum in a way that translates to the Google Form. Since that post was deleted, I would just like to reiterate that the offer was made in good faith (and still stands).
Curious as to why you say so. Not the kind of sentiment that I get from users of Lovable, Cursor and Weweb.
Logically speaking any product/service with users will have a vocal minority. I get plenty of haters in my own products. It sucks because they affect adoption within their organizations. Adoption is the key KPI for these projects.
Regardless I can only implement so much feedback over an X amount of time since I’m a solo developer.
Some requested features do require improvements to existing features in production, in order to be implemented.
I frequently have to push out beta features in order to get real user feedback. They mostly come in the form of complaints. I assume the lack of complaint means a feature is at least “good enough”.
Anyway back to the question. What makes the other companies you mentioned better at user feedback than Bubble?
One mistake I think the bubble team does make, is not fully utilising the bubble community.
I mean, it’s an entire community of amazing developers! Not only do we make UI’s day in day out but we also use Bubble day in day out: we are the ones who knows what we need - and have the skills to convey it.
So with a redesign like this for example, it could have been an idea to invite the community to participate in the initial design concepts and maybe even build prototypes in bubble itself, with the best ideas influencing the official design.
Point is, there’s a wealth of talent right here in this community, who are passionate about bubble and would be happy to lend their skills. Just something for the team to keep in mind for the future. 
We loose too many time to acces to workflow… it should be at first page, one click …