Bubble is horrible in every way! Changes aren’t saved, there are constant crashes, extreme slowness, and groups disappearing out of nowhere.
If I’d known it would be like this, I wouldn’t have even started using this platform for my project, but unfortunately, it’s too late to change now.
@miracle do you have an open ticket with the support team? If you do I would recommend you follow up with them directly there for the latest updates.
If you don’t, submitting a support ticket would be the next step to try and get this sorted.
Same recommendation for anyone else experiencing this: please submit a bug report
They are actively working on this. Have an opened ticket
I have an open ticket as well, are you also noticing poor rendering and inconsistent performance?
We are still actively looking into the different potential issues, some of them we’ve addressed and obviously others that we have not yet. We will keep everyone informed as we make progress. Best thing to do to help us is file a bug report - the more apps we have to profile, the easier it will be to track down the issues as these performance issues do not reproduce on all devices / apps.
I added this context on the support thicket but adding here in case anyone else is experiencing this. The loading when you first open the app is better (still slow, about 8 seconds). But once you get in the app it looks like things aren’t rendering because they haven’t loaded in, especially things with pictures. This is resulting the in the app being fully unusable at present. An example of this happening is as follows:
So it all seems to be stemming from a loading issue with several elements within the app. Happy to give as much context as needed - really need this resolved as the app is unusable and we are now 5 weeks delayed which sucks right now since we are trying to fundraise but have nothing to show.
I’ll also add none of these issues were experienced in the web testing environment or BubbleGo, this is exclusively an issue with the live app
Any luck in finding the root cause of the slow down?
Thank you for the added context, we are actively digging into it
Mine got fixed. Thank you Bubble Team!
Before, Android took 90+ seconds to load initially while iOS toom 20+ seconds to load initially.
Now Android takes 7-8 seconds which still needs to be a bit better, while iOS takes 2-3 seconds which is production ready.
Here is the response I got from the team on a week ago.
Hey all, adding this here in case it’s useful (or not) - this could be fake news, would be useful to get some input from a bubble employee @nick.carroll
I am about to launch my first mobile app and I asked Claude AI to explain the difference between new builds and OTAs for me so I could understand properly.
Claude told me that app versions which include an OTA update will load and run slower than an app version that doesn’t include an OTA update because the OTA isn’t part of the original package and takes extra time to load from bubble servers (in a different way).
I have no idea whether this is true but thought it interesting and worth sharing.
Even if I’ve never launched an OTA, I follow it could be interesting to know..
Normally, the initial app load after an OTA update takes longer because it needs to load in the new code, but we shipped any update yesterday where the code will load in the background and then be applied on the second app load which means there will be no user visible impact to app loading performance. The app itself wont run any faster or slower than the base app version though.
@nick.carroll @fede.bubble I am noticing some issues after this update. When i pushed an OTA and then deprecated all old build.
In our app, I have action that run on page(Index view) load.
A user opened the app, unable to run this action because they are still on the old build, and all access to the server is disconnected because of the deprecated old build. But in the background the new OTA has loaded but not yet running.
So the user will have to close the app and reopen it in other for the new update OTA to run on the app.
This is making our users open the app twice.
What’s the best practice here? or is this a bug
The reason i am asking this is because the popup that shows after you push an OTA says that changes will “appear the next time the app is opened or restarted”. But that is the time the OTA will be loading in the background?
Any help or clerification.
Thanks
On my side, OTAs take around 10 minutes to propagate and users mostly see them when they logout and the next time they login, or when they close the app..
OTA are currently alittle tricky for sure.
