Try splitting complex pages into nested reusable elements. We were having huge slowdowns as described here (20 seconds + per action/dynamic data change) and crashes claiming out of memory despite being on powerful computers with 64GB RAM, and were able to mostly resolve it by taking the most complex groups and splitting them out into reusable elements. No more crashing/major slowdowns.
That being said the current editor is a bit glitchy, I’ve found myself needing to refresh more often than I used to lately.
Yep, I use Safari for Bubble. There are some old glitches like playing hide-and-seek with WFs (when steps are not displayed) and dynamic expression building in Data Source (popup to choose type of thing to search for hides very often), but can’t say that I suffer from some slowleness (there are not so many elements on the page).
Same here. It is been incredibly slow where it has reached the point of the whole page jsut crashing (getting the Out of Memory error in Chrome). I contacted the support and one their suggestions was to use a more performant laptop (I am currently using a gaming laptop lol). Embarassing
They should not do this, I was convinced to buy a new laptop which didn’t improve the speed at all. I think Bubble are using standard responses to pacify their customers to this issue.
I submitted a Bug Report yesterday, don’t know how many of you have, but got a swift response from the team, hopefully escalating the issue helps them realize the actual problem. I even shared them the link to this thread, so they can see it by themselves.
Has anyone found that today things are a bit smoother? Support answer was: “there are no problems we can reproduce from our side, please regularly clear the browsers cache, and/or use the editor in Incognito Mode” which I simply find unacceptable.
I asked support to not tell me they are looking into the issue because they said that a year ago. I then got a reply apologising and saying that they are looking into it.
I had an idea which would be easy for Bubble to implement I think. The main sticking point (for me) is the workflow tab and I assume that is because it needs to load the whole app’s workflows. Why not only open workflows relating to the users’ first workflow folder. They can insist that all workflows be assigned to a folder so then it’ll make loading much quicker I think.