kmp-navigation

Type-safe Kotlin Multiplatform navigation is built using a modular Navigation 3 pattern with @Serializable route objects. You define route contracts in :api modules and wire them using Navigator and EntryProviderInstaller to ensure compile-time safety across platforms.

Per-route ViewModel lifecycle management in Compose Multiplatform navigation is handled by assigning unique keys to parametric routes. This ensures ViewModels are correctly scoped and maintained across Android, iOS, and Desktop when navigating between screens.

Yes, Koin can be used to wire navigation routes in a Kotlin Multiplatform project. The architecture centralizes dependency injection in :wiring-ui modules using EntryProviderInstaller, connecting Koin-provided ViewModels to their corresponding type-safe routes.

The best way to handle screen transitions in Kotlin Multiplatform Compose is through metadata-based transitions. This approach attaches transition configurations directly to type-safe route objects, enabling smooth screen animations across Android, iOS, and Desktop.

Navigation contracts are shared across Android, iOS, and Desktop in Kotlin Multiplatform by defining type-safe route objects in :api modules. These contracts are then exported to iOS via a :shared module, reducing boilerplate and platform drift.

Passing arguments with parametric routes in Compose Multiplatform navigation requires using @Serializable route objects. This method enforces type safety for navigation arguments while managing per-route ViewModel lifecycles with unique keys.