Migrate from Fresco to Coil?

[nicolas-raoul]

Coil was recommended as a more stable alternative: #6410

Is there a consensus that it would be better?

[RitikaPahwa4444]

Thank you, @nicolas-raoul, I was about to create an issue for this 😄 We're using glide already at several places in the project, so that's another option we have.

[rohit9625]

Hmm, so we should just stick to one image loading library; it can be Glide or Coil. I'd go with Coil as I've already added that library in the PR that migrates the Custom Selector to Jetpack Compose. Migrating from Fresco can also decrease the size of APK, as I noticed the increase in size of APK after bumping the Fresco version to the latest.

[RitikaPahwa4444]

Oh, the APK size has also increased? 🥲 I don't see Coil integration in the code base at the moment. Both are recommended for Android in the official documention, so any of them should work. Glide seems more popular; at least from the GitHub stars count. But we need to evaluate the performance impact and APK size before we choose one.

[rohit9625]

Oh, the APK size has also increased? 🥲 I don't see Coil integration in the code base at the moment. Both are recommended for Android in the official documention, so any of them should work. Glide seems more popular; at least from the GitHub stars count. But we need to evaluate the performance impact and APK size before we choose one.

Yep, you're right. In this case, we should migrate to Glide instead of Coil, as removing Fresco is the main motive behind this migration. How can we distinguish between performance of Glide and Coil?

[RitikaPahwa4444]

https://developer.android.com/develop/ui/compose/quick-guides/content/load-images#load_an_image_over_the_network

It does say Glide offers smoother scrolling and is fast, will have to dig deeper to find the performance benefits they offer

[RitikaPahwa4444]

#6665 (comment)

Interesting input from @neeldoshii. Beyond performance, we need to check our use cases as well. If Coil supports them out of the box, we could choose Coil.

[neeldoshii]

If Coil supports them out of the box, we could choose Coil.

Both Glide & Coil supports caching & performance. But I am more inclined towards coil for compose. As support for glide is in beta phase even its been 5 years since the launch for Jetpack Compose.

Glide’s Compose integration is in beta. Please submit bugs if you encounter any and/or feature requests to Glide’s Github Issues.
Source : https://bumptech.github.io/glide/int/compose.html

Even Google Recommends Coil :

Load an image from the internet
To load an image from the internet, there are several third-party libraries available to help you handle the process. Image loading libraries do a lot of the heavy lifting for you; they handle both caching (so you don't download the image multiple times) and networking logic to download the image and display it on screen.

For example, to load an image with Coil from Instacart, add the library to your gradle file, and use an AsyncImage to load an image from a URL:

Source : https://developer.android.com/develop/ui/compose/graphics/images/loading

[RitikaPahwa4444]

Google recommends both but beta for 5 years sounds odd. In that case, let's go with Coil.

[github-actions]

Hi @RitikaPahwa4444! You have been assigned to this issue. ✨