Image Load Time 1 minute + & Excessive App Storage

Mobile Beta
1

Hey again!

So my app is a clothing marketplace which obviously requires a tonne of image loading and thus caching. After testing my app over the past 4-5 days, I’ve gone and seen that BubbleGo has racked up 1.2 GB of storage on my phone. This is disasterous if I were planning on releasing this to the public. So my question is:

Does BubbleGo generally store more data than a testflight version of my app?

Is there a way to control which image data is stored locally?

Is there a way for images to load faster?? (I have seen many forum posts on this, and am wondering if anyone has found a solution. Is BubbleGo load-time the same as a fully-released app?)

Can we prioritise the Bubble.io team’s focus on image load time, storage, and loading events before launch? Noting that @nick.carroll has put this as a area of concern that will likely have to wait until after public release (which we all know could be a while longer)?

2

Can confirm that no difference is found between testflight (LIVE) app and BubbleGo.

3

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.

4

Thanks for flagging this. We are definitely aware of long image loading times and will be investigating why this is the case soon.

In the mean time, we’ll also take a look into how someone might clear stored data on the app if it starts taking up a lot of space.

2 Likes
5

Thanks Nicky mate your the best! I’d personally say your prioritise from my experience are

  1. Add conditional state for image “is loading”
  2. Better optimize image storage (maybe add a box on images - is locally stored, or isn’t, because some images we want loaded instantly, and other we are happy to load each time the app is restarted)
  3. Image load time - still an issue, but definetly less concerning for me personally after adding the Imgix Pjpg property spoken about above - load time under 2 seconds now which is OK.
1 Like
6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.