an opinionated look at Googles library collection
summary
Google's Jetpack lists 115 artifacts but many are duplicates, outdated, or poorly categorized; documentation misses subordinate modules and shows legacy libraries that no longer make sense. A demo Compose app actually uses Palette for Palette color extraction from photos (via the photo picker), plus appcompat, activity‑compose, lifecycle and activity result contracts, and it works; Emoji2 exists but Emoji2 uses views so it needs wrapping for Compose. Recommendation: prefer fewer, current modules and enable baseline profiles for startup cost.
AI-written summary · about
chapters (10)
- 0:00Jetpack introduction
- 1:52Why Jetpack was introduced
- 6:31Jetpack's changing role
- 10:48Jetpack library categories
- 13:18Duplicated and legacy Jetpack libraries
- 23:03Niche Jetpack libraries
- 26:42Demo: Palette library
- 31:47ComponentActivity pitfalls
- 34:18Emoji 2 library usage
- 36:13Summary: Jetpack adoption
related talks
01h 18mArt of Jetpack Compose
41mCompose by Example
55mRoundtable Discussion: Ask Googlers About Android Jetpack
01h 09mJetpack Compose for consistency of your apps' UI
35mSomething old, something new: Adding Jetpack Compose to a large open source Android app
29mWhat's new in Android
49mNavigating with Jetpack Compose
37mSomething old, something new: Adding Jetpack Compose to a large open source Android app
