Workshop: Choosing Your Compose Multiplatform Navigation Stack

What We Will Build By the end of this workshop, you will have a working mental model — and working code — for the three navigation solutions in Compose Multiplatform: Decompose , Voyager , and the official Compose Navigation . I will show you the same two-screen flow (Home → Detail with a type-safe ID argument) implemented in each, so you can compare them side by side and pick the right one before you are three months into a project and regretting your choice. Prerequisites Kotlin Multiplatform project targeting Android + iOS (Desktop is a bonus) Compose Multiplatform 1.7+ configured Familiarity with @Composable functions and basic state hoisting Step 1: Decompose — Own the Lifecycle Here is the minimal setup to get this working. Decompose gives you a ComponentContext tree that owns your navigation state independently of Compose. This is the pattern I use in every project where lifecycle complexity is real. class RootComponent ( componentContext : ComponentContext ) : ComponentContext