Skip to content

Latest commit

 

History

History
17 lines (13 loc) · 1.5 KB

File metadata and controls

17 lines (13 loc) · 1.5 KB

Why choose the "Coil" to be the Image Loader library?

According to Top 10: Best Android Image Loading and Caching Libraries , there are common libraries such as Picasso & Fresso & Glide and so on. The "Coil" attract my sights because the below description:

An image loading library for Android backed by Kotlin Coroutines.

Coil is an acronym for: Coroutine Image Loader. The coroutine is the asynchrous operation for modern android design.

For deep diving to learn and understand coroutine, I should pick up this one

  • Fast: Coil performs a number of optimizations including memory and disk caching, downsampling the image in memory, re-using Bitmaps, automatically pausing/cancelling requests, and more.
  • Lightweight: Coil adds ~1500 methods to your APK (for apps that already use OkHttp and Coroutines), which is comparable to Picasso and significantly less than Glide and Fresco.
  • Easy to use: Coil's API leverages Kotlin's language features for simplicity and minimal boilerplate.
  • Modern: Coil is Kotlin-first and uses modern libraries including Coroutines, OkHttp, Okio, and AndroidX Lifecycles.

Why the Service might be killed in different timing from a variety of devices?

Please refer to dontkillmyapp It provides a list which OEM is the killer for service, I guess this way could protect and remain the OEM's main bundle APP