This is probably an ok idea…but I have 2 apps I’ve built. One is live, and the other is about to go live. I haven’t had any of the problems talked about. My editor doesn’t crash, etc. Then again, I only use 3 or 4 plugins, and I’m about to get rid of a couple of them.
So, I’m thinking most of the problems are probably from more advanced apps that are a lot more detailed than mine. So, just building an app may help a little but maybe not a lot as in my case.
I like that Bubble is making changes, but just letting everyone beta test them could be why there aren’t a whole lot of complaints about things…most of those testing them may just have simple apps.
I think Bubble should put together a team of people with some of the most advanced apps and let them test the changes first and give feedback. They would probably get better feedback.
Employees are always the best at making suggestions…and in this case, users who have large apps.
Maybe they already do, I don’t know, but there are obvious problems that need to be addressed.
bubbles equivalent of the “blue screen of death”…
how long must I wait to load my pages and reuseables…
used to load near instantly, now I have to wait almost a minute.. ok over a minute (it just finished loading! - took the same time to load as it did to screenshot it and write half this post on the forum!)
even after loaded initially it is delayed on every reopen… super downgraded experience and pure frustration every few seconds of development now. It’s like going from fiber optic back to dial up.
To be fair to staff at Bubble, the buck stops at the top. Their hands are probably tied and the recent departures of several key Bubble employees probably is a good indication of this. @josh and @emmanuel is ultimately responsible for the growing displeasure within the Bubble ecosystem.
Every engineer should be made to read the forum first thing in the morning without failure, specifically the Bugs section. Anybody who contributes to deployments should see first hand the results of their work, both good and bad.
Hi. I generally like this update, but loading times for the App Manager are a bit painful (I have a very large app). Could folder contents be loaded on demand rather than immediately to help this (for example, all my custom folders could be hidden until I open them)?
I find it is pretty rare that I scroll through all the Pages/Reusables rather than searching for a specific one. So, for me, hiding the Web and Mobile folders by default would not be an issue if loading times were faster. Or could I search without opening the dropdown list?
Adding New Pages, Reusables
When setting up a new View/Reusable, I have to open the dropdown and wait. If the “+ New” button was moved to the header bar (see the red arrow), there would be no need to load the full list when I have no interest in seeing it
U need to fire whomever that suggested. Just use the same layout like in any IDLE and the same simple pattern like in React ( where even 5 y.o kid can understand what to what belongs to )
Please allow us to disable the previews that open on hover, like we could do before. We have so many pages that this ends up nearly crashing the page as I move my mouse over them.
Yeah that’s the silly part. One would think that after it loads once, it would load fine afterwards. But that also doesn’t happen.
And many times after waiting for minute when it loads, the browser crashes after “please wait pop-up” (or my brain crashes first, trying to remember which page I was trying to go to)
This update is driving me crazy. Reloading the editor every 5 minutes, it’s freezing, adding App Text takes 15-20 seconds, switching between reusables and pages takes 10-15 seconds.
But my additional request would be that while this particular release has been very very bad on the editor performance, it has been happening for a while. In last year a lot of changes that have been made in editor have made the editor unusable gradually.
Somewhere something fundamental needs to be checked on how Bubble editor is built, how it handles memory, how it optimises performance, how it can give option to people to work fast instead of frills which look good just for marketing e.g. element preview on hover etc.
Like you people have done in past, please do not come up with some band-aid solution like adding an extra url parameter to remove caching or having a checkbox to command whether error checking will be done on backend workflows in real time or not, or some such. Fundamentally the editor needs to consume less resources!
And please test on large apps before releasing these shiny toys!
) but if the trade off is I can actually get work done, its worth it. Live saver!
