Migrating Android apps from Fragments to Jetpack Compose
summary
Turo’s migration approach introduces an open source library Nibel that uses KSP code generation to create typesafe screen entries and a unified navigator handling fragment⇄compose⇄compose flows. Generated fragment or composable entries let the system choose fragment transactions or Compose Navigation under the hood, reduce fragment allocations for internal flows, and support multi‑module destinations via a shared navigation module. The library preserves backstack across config changes and ships as a working GitHub project ready to integrate.
AI-written summary · about
chapters (19)
- 0:00Start
- 2:07Navigation scenarios
- 4:01Jetpack Compose architecture
- 5:17Navigating fragment to compose
- 6:22Navigating compose to compose
- 7:37Navigating compose to fragment
- 8:42Wrap composable with a fragment
- 10:13Base fragment class
- 12:33Navigation-fragment transaction
- 14:11Generated composable wrapper
- 14:41Implementation type
- 16:06Navigation under-the-hood
- 27:44Navigation module
- 29:35Declaring a destination
- 30:16Associating a destination with a screen
- 31:09Navigation fragment to compose
- 33:40Scenario 1
- 35:33Scenario 3
- 37:08Blog posts
related talks
32mMigrating Android apps from Fragments to Jetpack Compose with Nibel
38mFrom Android View to Jetpack Compose — A Guide to Migrating to Jetpack Compose
35mPainless, Typesafe Jetpack Compose Navigation with Voyager
19mUsing Jetpack libraries in Compose
01h 09mJetpack Compose for consistency of your apps' UI
33mMigrating to Jetpack Compose - an interop love story
42mRoad to Single Activity
47mUp to Date? Talking About Your App