Why Jetpack?
summary
Jetpack is a set of independently versioned AndroidX libraries distributed via Gradle/Maven that let apps move functionality out of the OS and into APKs. Highlights: WorkManager replaces ad hoc job schedulers and guarantees deferred work, Navigation generates safe argument plumbing from an XML graph so deep links and fragment transitions are typed, and Room gives an easier async SQLite layer. Jetifier (rename tool) currently breaks some codegen libraries — Glide is a known casualty — so enable it cautiously. Recommendation: adopt Jetpack components as the default and swap them out only when they fail your needs.
AI-written summary · about
chapters (16)
- 0:00Introduction and speaker background
- 1:55What is Jetpack and its purpose
- 3:59Problems with Android development before Jetpack
- 7:06Google’s internal framework and its limitations
- 9:34Jetpack as a solution for teams of all sizes
- 10:38Jetpack as a right way to build apps
- 13:28Jetpack components overview introduction
- 13:51What is AndroidX and Jetifier
- 17:23Navigation component deep dive
- 20:53WorkManager for background tasks
- 22:37Room for database management
- 25:07ViewModel and lifecycle components
- 26:30LiveData and RxJava comparison
- 27:33Missing Jetpack components and future wishes
- 29:18Jetpack resources and related talks
- 30:00Q&A and closing remarks
related talks
01h 13mAccelerating Android Development with Google Jetpack
43mTo infinity and beyond: what's new in Jetpack for Android professionals!
30mJetpack
34mAndroid Jetpack: What's new in Architecture Components
14mWhat’s new in Jetpack
43mAndroid Jetpack ❤️ Kotlin: On the road to more wholesome APIs
19mWhat's new in Jetpack
29mWhat's new in Android