Skip to content

Instantly share code, notes, and snippets.

@vtthach
Created June 26, 2017 13:06
Show Gist options
  • Save vtthach/91dfb7dc31c9c247e8af05b9b7f1d784 to your computer and use it in GitHub Desktop.
Save vtthach/91dfb7dc31c9c247e8af05b9b7f1d784 to your computer and use it in GitHub Desktop.
Picasso v/s Imageloader v/s Fresco vs Glide
There are many different libraries available out there to load images when you develop Android applications. Picasso has been my favorite which is light weight, but functions provided are more or less similar to Imageloader and Glide. Most libs have callbacks but Fresco does not, which seems to have the best performance compared to all other libraries. So I thought, a simple comparison of these different libraries would help fellow developers when they want to select the best image download library for a specific requirement.
Fresco
(Cons)
- Huge size of library
- No Callback with View, Bitmap parameters
- SimpleDraweeView doesn't support wrap_content
- Huge size of cache
(Pros)
- Pretty fast image loader (for small && medium images)
- A lot of functionality(streaming, drawing tools, memory management, etc)
- Possibility to setup directly in xml (for example round corners)
- GIF support
- WebP support
Picasso
(Cons)
- Slow loading big images from internet into ListView
(Pros)
- Tinny size of library
- Small size of cache
- Simple in use
- UI is not freeze
- WebP support
Glide
(Cons)
- Big size of library
(+)
- Tinny size of cache
- Simple in use
- GIF support
- WebP support
- Fast loading big images from internet into ListView
- UI is not freeze
- BitmapPool to re-use memory and thus lesser GC events
Not every library contains all functions. I usually use Picasso and Glide. If need speed and low quality go with Glide else Picasso would be good too with high quality images and caching.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment