I tried. I really did. I use it consistently since I got access to it without switching back until I just couldn’t take it any more.
It’s terrible.
I have to click and average of 3 to 5 clicks more for every edit. I have to move my mouse all over the screen as the windows pop open. It is so inefficient it has actually slowed my editing down, not to mention the carpel tunnel impact from additional clicks and mouse movement.
I have trouble believing this passed any sort of actual UI/UX testing.
Yes…everytime I see it I immediately turn it off. Updates are slow, as takes 3-4 weeks between updates which are usually less than 5 improvements, which are improvements as they realistically are just getting original editor functionality back into the new debacle.
Yes we nearly all feel that way. No matter how many times we say it, they will cherry pick irrelevant metrics to tell us we loved it when they force it down our throats.
Good news is with Buildprint and/or a bunch of other AIs you can spend less and less time in the editor…
funny how Bubble is all in on visual being the future of dev and being their moat and yet are regressing on that very strength…
I’m hoping @josh and @emmanuel are thinking along same lines and a shift toward the underlying infrastructure of Bubble as a Platform as a Service and Backend as a Service, to be seen as their main product and they create a moat around that.
Not sure what that means but it doesnt seem too feasible to make such a moat in todays world where anyone can just build such a wrapper around a codebase
Hey James, totally hear you that it’s been adding clicks to your workflow. I’m hopeful that some of the improvements we’re working on, like removing popovers such as the constraints or dynamic expression flyout, will help make building feel efficient again.
Are there any workflows you’re thinking of that feel particularly inefficient?
Bubble has for past several years said their product is the visual editor, it is not, it is the infrastructure they provide; that’s Platform as a Service and Backend as a Service.
I wouldn’t say anyone can just build anything…still takes time, still dozens of reasons why people wouldn’t. I don’t even understand what you mean by a wrapper. A wrapper for what?
Yikes! If the real product is supposedly the infrastructure and not the visual editor, then Bubble spending years telling everyone the editor was the moat is a pretty bad sign.
Even using AI in the browser without a framework , I’m sure you see how easy it is to stand up the basic infrastructure layer like a server, database (and option sets) and RLS.
So if that is what you mean by Bubble’s moat / product it won’t be of any value to allow Bubble to function ast a B/PaaS?
If you mean something broader than that, what specifically is the infrastructure advantage you think Bubble has?
AI and the editor APIs make this true…your Bubs and buildprint are public displays of this. I’ve been saying for past year, the editor is not the product and should not continue to be revamped with visual tweaks, because I was bypassing editor to build.
What the infrastructure is, is the backend, the security, support etc. if you built Bubs, and feel infrastructure of Bubble is not the product but the editor is, you likely feel Bubble is a sinking ship.
For me, I see Bubble as in a position to do incredibly well, if they fully embrace OPM and allow more 3rd party tools to leverage AI and the editor APIs, so Bubble can get back to fixing Bugs, launching new features from idea board and getting mobile out of Beta. I’d hate to see them waste more time on AI stuff, especially things like remixes and continuous tweaks of editor look.
I said before Bubble announced their AI could do designs, they should leverage OPM and just let Figma do thei Figma AI and fix the Figma import feature. What happened? Bubble bought a Figma import plugin, and still gets excited to announce their AI LLM provider they use released a new version that improves Bubble AI design, only to be met by community members pointing out the still lackluster results.
So, yes, editor is part of product offering, but it’s not their core product in 2026 and beyond. Just like AI is changing SaaS where the UI matters much less, and the APIs are more significant, Bubble needs to see that too.
I really hate it… and for some reason I cannot come back to the old version of the editor… I have been fighting for months to not switch to other nocode tools or “classic code” despite a lot of people encouraging me to switch, but I feel the new editor is the reason I am going to switch… It is sooo buggy, sooo counterintuitive and ineficient, I cannot believe it has been approved by UX/UI testers
Technically it is still in beta , so maybe now is the very best time to capture those bugs, make improvement suggestions, etc - ie be part in helping shape it. (I understand that not everyone has the time for that of course).
, I’m sure you see how easy it is to stand up the basic infrastructure layer like a server, database (and option sets) and RLS.
