Migrating to Paging library
summary
Migration shows concrete changes: replace RecyclerView.Adapter with RecyclerView.Adapter → Paging library migration and switch to immutable lists and a PageListAdapter, pick one of three DataSource implementations (positional itemKey pageKey DataSource types), tune config (example uses pageSize 30 default loadSizeHint = pageSize×3), and handle network+DB with a BoundaryCallback that requests pages and saves into Room (BoundaryCallback triggers network loads and writes Room). Evidence includes adapter behavior, null-item placeholders, and data-source invalidation/recreation.
AI-written summary · about
chapters (10)
- 0:00Start
- 7:08Updates - the truth
- 15:36Placeholders
- 17:20RxPagedListBuilder
- 17:45Under the hood
- 20:46Data Sources
- 28:47Database + Network
- 29:52Data switching
- 30:46Data layering
- 33:22Paging Library
related talks
34mMigrating to Paging Library
36mImplementing the Paging Library
33mAndroid Jetpack: Manage infinite lists with RecyclerView and Paging
41mEfficient Lazy Loading for RecyclerView with Room
36mJetpack Paging Library 3 in Real Life
34mInside Android KTX
45mGraywater: A Framework for Fast Scroll Performance
42mRecyclerView 13000