Image Loading With Fresco: 4 Years Later
summary
Fresco tracks four years of changes: a production 1.0, modularization into 23 Maven artifacts, and a major 2.0/2.1 bump for AndroidX and optional native loader swaps. It uses a three-layer pipeline (decoded memory, encoded memory, disk) plus network, handles progressive JPEGs, and warns that a 12MP JPEG decodes to 46 MB decoded bitmap. New VTO UI uses immutable image options and offers Java-only builds and native decode-time rounding for much faster rendering.
AI-written summary · about
chapters (9)
- 0:00Introduction to Fresco
- 1:03Fresco evolution over four years
- 3:13How Fresco works under the hood
- 12:00Image pipeline and caching layers
- 18:18Modularity and native code support
- 22:09Improving image performance
- 28:46Rethinking Fresco APIs
- 31:35New UI components Fresco V2
- 37:56Q&A and resources
related talks
41mFrom ImageView to Compose: Architecting Image Loading
35mImages 101
32mImages 101
34mImage Alchemy: Efficient Processing of Images
35mPractical Image Processing in Android
01h 01mAn Android Retrospective
53mGraphics Something Android Something Performance
45mUncoiling the COIL - Modern Image Loading on Android
