If your internal QA team spent a day building an app in Bubble, they’d quickly reproduce every bug I’ve reported (particularly once that app gets to a decent complexity in reuseables and elements) —plus many other bugs I haven’t bothered to list.
I understand Bubble is complex, but basic QA shouldn’t fall on users, especially when these bugs have persisted for weeks or months and are core functionality that is broken. Many issues surface after a few hours in the editor and seem tied to memory problems. Frequent refreshing helps temporarily but becomes a serious time drain, and mental strain (losing my thought process) especially in larger complex apps.
I’ve also noticed time-based performance issues. The editor becomes slow and buggy for hours for no reason, then suddenly gets fast and bug free (without even a page refresh), suggesting potential server-side issues. This seems to happen both on client side page loads and editor - so it’s not just editor memory issues but a server-side issue. I’ve tested other platforms and media heavy websites and done speed tests when this issue occurs (my internet is consistently 200mbs+ up/down with 3-4ms ping) and they don’t have any issues so I can narrow it down to being a bubble server-side issue.
Please consider assigning someone internally to build a full app from scratch. Most of the bugs I’ve listed cannot be reproduced in isolation and will only happen during sustained use of the editor for a few hours. They’ll experience these problems firsthand and can log them in the format you need to resolve them.
Bubble is a great platform, and I hope these bugs are addressed soon for the benefit of all users.
I’m seeing a new bug where navigating to an action/workflow from the logs “Zoom in on workflow” breaks the entire workflow/action view. Consequence of the new workflow editor. No need for “reproduction steps” it just always happens when using “Zoom into workflow.”
My greatest source of bugs/buginess has always been from reusables. I refuse to use them outside of cases where they’re absolutely necessary for this reason.
Anyone struggling to submit a bug report because the AI bot gives at least 5 turns of crap AI resolution attempts without sending me to the bug report flow?
What I find truly fascinating is the range of experience between developers. Like there’s some who have no single clue what is being referred to regarding browser crashes (out of memory), like they have literally never experienced it Whereas for others its virtually hard wired into their bubble experience. A lot of the bugs I see reported in this thread, and others, I have no experience of. There’s a bunch of things I do have to deal with and accept but I seldom see them mentioned elsewhere - though that could be the case that, like myself, I don’t bother reporting them as a) its a drag of an experience b) I believe it will just be ignored/brushed off anyway.
Just intrigues me that there is a large variation in editor bugs that you come to accept as “just Bubble things…”
It’s insane it’s so normalised though, like incompetency and barely-functioning features are just “the way”. So many hacks/solutions/plugins that do little more than adjust tiny settings Bubble seem to not be bothered to do themselves or simply have no interest in and I worry it’s starting to damage the brand at this point.
I believe many of the issues with Bubble stem from two key factors: the complexity of the app and the amount of time spent in the editor.
As your app becomes more complex, the editor has to load more elements, which increases the likelihood of performance issues.
The longer you work in the editor without refreshing, the more memory accumulates—leading to slowdowns, glitches, and eventually crashes.
Performing heavier tasks, like using the search tool to jump through dozens of references in a large app, often triggers instability.
For most Bubble users—especially hobbyists building smaller projects or working in short sessions—these problems are unlikely to surface. Simpler apps just don’t put enough strain on the editor to expose its limitations.
However, if you’re building a production-grade app and your project continues to grow in scope, the frequency and severity of bugs and crashes increase significantly. At a certain point, the editor may crash multiple times an hour during intensive work.
The real concern is that once you reach this point, it becomes a point of no return. You’ve likely invested so much time into building on Bubble that switching platforms becomes extremely difficult and you are very locked in.
@fede.bubble could we please get the bug report form back. You guys can keep the AI chatbot too, there is no reason we can not have both.
@fede.bubble is the above still the same metrics bubble is using in guiding the decisions around such a simple fix, to bring back the bug report form at the same time keeping the AI chatbot?
This happens with all software. Hard to account for all edge cases. I know a lot of these problems come down to bloated apps, large numbers of users, or extensions/plugins.
I have suggested the team for workflow editor filter type by outer group. For click elements.
Lets say you have 1000 wf’s in a page due to it being SPA, 10 main groups serving as pages each 100 wf each group. It would serve as a automatic foldering system, improving wf navigation significantly for complex apps.
They didn’t seem to care.
I think main problem is ‘‘Bubble is not for only MVP’s anymore vision of Bubble’’ is not well communicated within organization structure
I am happy to see that we are all in agreement that bubble support only look at the past 1 message. Most of my answers to support is. Please read my message 2 messages up.
e.g
me: Watch this recording of the bug and how its happenieng {Link}
me: Do you think this will be able to get fixed this week?
Bubble: Hello for us to progress with any tickets, we need replication steps
me: Do you read chat?
I no longer bother with bubble support unless its p1
add a new element to the page, go to workflows to setup action to show the element, element is not in element list and need to refresh page in order to have it show in the element list. TERRIBLE EXPERIENCE…need to refresh browser after almost any change now.
A simple fact based on my experience is that the editor has been more unreliable and buggy than ever. I have used it professionally for around 3-4 years now and it’s MUCH more buggy over the past few months I’d say, maybe with the visual newish updates to the editor.
Now I know it might be that I am working on the biggest project I have worked on and I have gone reusable crazy (still lest than 100 re) as that is the SUGGESTED pattern when working on single pages apps for editor performance.
If they wanted to squish bugs they should make it easier to provide good bug reports. Why not have an in editor bug submitter which provides context to the report by it just being in the editor.
@fede.bubble could engineering do a test where they scale up the amount of reusable and see if that tanks performance of the editor. That is the only thing that has majorly changed over the past month for me, and I noticed others are talking about reusables in this thread too.
As for what bugs…its hard to tell as there is so many glitchy weird things that literally happen multiple times an hora let alone just plain old crashing of the page. If i tried to bug report, and be detailed on every bug I’d literally spend most of my day doing it.
As for how this is affecting my relationship with Bubble… well my mind certainly starts drifting into how I might protect my career if Bubble keeps this up as the platform ‘feels older’ by the second.
On the bright side, it’s been the right kick in the butt to get me to start putting heaps of hours into learning python and other backend infrastructure.
