Noticed that Accompanist-Glide library is now deprecated (as of v0.14), had some questions around th...

# compose

[Tash]

Noticed that Accompanist-Glide library is now deprecated (as of v0.14), had some questions around this:
• Why was this done? Is Coil the recommended official solution?
• For existing Android Views that use Glide, is Glide -> Coil migration now a pre-requisite of Android View -> Compose migration?

[Tgo1014]

It’s kind explained on the changelog: https://github.com/google/accompanist/releases/tag/v0.14.0

[cb]

Why was this done?

Because we no longer had time to maintain it, and none of our samples, etc were using it. Accompanist was and always has been an incubator for things which aren't quite available yet. With Coil migrating away, it didn't make sense to continue working on Glide.

Is Coil the recommended official solution?

It's not an official solution, but it is the solution which I recommend. Glide is very much built on top of views, and has a lot of assumptions and hooks which assume that it will be run on views. The Accompanist library had a lot of hacks just to make Glide work.

Coil on the other hand is Coroutines based image fetcher, with some light integration for views. Compose + Coroutines = ♥️ , which means that the integration for Coil is pretty seamless.

[cb]

Is Glide -> Coil migration now a pre-requisite of Android View -> Compose migration?

Not necessarily. There are other libraries available which support Glide, such as Landscapist: https://github.com/skydoves/landscapist

[cb]

Also, Accompanist is open source so anyone is free to take the code, fork it or use it.

[Tash]

Thanks for the explanations Chris! Sounds good 👍🏼