Is anybody using an efficient and common file format for image assets across platforms, especially on Android and iOS? Webp is possible. There are several iOS libraries and SDWebImage looks good. Seems like using the same assets, even just the same process for converting assets would offer efficiency for a cross platform development team. I got a (IPA max) file size problem to fix with efficient formats and I want to solve it for the least number of design team file conversions and the fastest rendering.

We use WEBP on iOS. It works great. Not much to it lol

Do you use SDWebImage or some other library to decode it?

We use SDWebImage to decode it. I have had zero issues and it's cut the size of our images by a huge amount. It's really reduced everyone's bandwidth costs.

@Elizabeth Mezias what is your goal? just load and show images on your App's UI or process the images on background for some business logic?

The images are static and it is mostly load and show them in the app. There are some animations. The goal is to reduce the overall size of the app by migrating to more modern, mobile file formats

so, in my understand, the goal of kotlin multiplatform (KMP) is

share the common logic between the platforms

, load/cache/show images on App's UI can be successfully achieved using the current libraries or frameworks, like

glide

or

coil

for Android, and the many libraries existent for swift in iOS (like

SDWebImage

) that do their job in the more effective way. So, in my point of view, load the image on kotlin side for native targets, just to load the image on UI, is not a good use of the KMP technology... unless, you want to do some specific job (business logic) with this image.

Thanks. You are right. That's good feedback. My goal is to evaluate some libraries that can improve the cross platform app building process and this is the best way to poll people about using WebP across platforms. I'm new to this Slack team. Seems like a reasonable question.

iOS has an on demand resource feature that you should look into. Basically, a separate resource bundle is uploaded to Apple and your app pulls down the ones it needs asynchronously at runtime. It acts like a cache, keeping around the ones most used and removing the ones least used on the device. Apple TV apps have to use this a lot.

Thanks, yes, that kind of dynamic loading is interesting. My team actually did code with Cloudinary using on-demand images. Network latency or an unavailable network (especially when app download and launch get separated) is a deal breaker for us. There are Apple Store IPA optimizations that help us. However, the test team gets a build with all of the (jpg/png/pdf) resources and all sizes in it and that it how you can hit the file size limit.