Migrating Android apps from Fragments to Jetpack Compose with Nibel
summary
Library Nibel generates entry classes so Jetpack Compose screens interoperate with fragments: add UI Entry annotation and KSP emits either a fragment wrapper or a lightweight composable entry depending on implementationType=fragment/composable. Navigation covers fragment→compose, compose→compose (uses Jetpack Navigation under the hood), and compose→fragment by locating the nearest fragment backstack entry; saved state and dynamic destinations are retained. Multi-module navigation uses explicit Destination objects. Demo builds and switches a screen from composable to fragment without compilation errors.
AI-written summary · about
chapters (12)
- 0:00Introduction to migrating to Compose
- 1:48Problem and gradual adoption
- 3:34Unified navigation goals
- 4:37Basic navigation experience
- 8:29Thought process behind solution
- 10:58Navigation between screens
- 13:24Implementation details
- 17:17Demo of generated code
- 20:35Multi-module navigation
- 25:48Adoption scenarios
- 28:58Conclusion and flexibility
- 30:07Q&A
related talks
44mMigrating Android apps from Fragments to Jetpack Compose
38mFrom Android View to Jetpack Compose — A Guide to Migrating to Jetpack Compose
36mNavigating the future with Jetpack Navigation 3
01h 09mJetpack Compose for consistency of your apps' UI
19mUsing Jetpack libraries in Compose
33mMigrating to Jetpack Compose - an interop love story
28mNavigation in a Multiplatform World
49mNavigating with Jetpack Compose