Hello,
Has anyone else noticed issues in BubbleGo with images taking a very long time to load wether they are uploaded or taken?
We are in the final stages of building and looking to send our app into approvals by the end of this week but I just want to know if this is more of Bubble Go issue. I’ve already contacted Bubble support and they haven’t found any issue with our set up. Could it just be a BubbleGo problem? Any insight would be greatly appreciated.
There are also other similar items on the forum.. I think it’s like that at the moment..
Oof that’s not great, very bad user experience.
I wonder if there is an ETA on fixing this
Yeah its not great… We have a ticket to explore why this is the case, but in the mean time we will expose a property that can be used to create a loading state while the image loads. We are heads down on build stability / bug fixing ahead of the launch so we probably wont get to exploring why image uploads take so long until after the launch
When will the property be created?
Hey @themmara did you find any way to increase load times of images??
AHA! Big discovery for Image Load-time. All my images are in Webp for optimisation over the web. I think when displaying this file type on mobile, some sort of image conversion is undergone, which both takes AGESS and adds alot to storage (likely transporting to PNG).
A fix I have found in the mean-time is to add the “processed with imgix” and most importantly setting file format to Pjpg which is seems to be the most optimized for mobile at the moment. Also reducing quality where applicable helps.
I still hope some focus can be made by the bubble.io team to implement a loading state for images, and maybe while there at it look into load time and storage optimization.
Ahh this is interesting, so far this has helped somewhat, but definitely still has a lag: This is feedback we received from bubble specifically for the flow where you upload or take a picture:
After taking another look at your workflow compared with the test workflow I created, the only notable difference was that mine didn’t have the additional “Show/hide” actions after setting the view’s image property. This may be related to the slowness you’re seeing, but would you mind testing this out on your end?
Adjust your current setup so that the image element that displays the uploaded image is already visible (on view load) at the start of the workflow, and then temporarily remove the additional “show/hide” actions from the end of the workflow.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
