kotlin-navigation-compose-multiplatform

Back-stack ownership in Compose Multiplatform requires a single NavController model to shape history. You enforce predictable behavior by using explicit NavOptions like popUpTo, saveState, and restoreState for screen transitions.

You structure typed routes by modeling explicit destinations with minimal, typed parameters. This approach enforces argument discipline and prevents passing complex objects directly through NavController routing logic.

Yes, the stable navigation2 integration supports robust deep-link handling across Android and shared code. It separates shared routing logic from platform-specific entry concerns to maintain coherent multiplatform routing.

The best way to decouple leaf composables is by establishing centralized NavController ownership and using event-based navigation. This ensures screens emit events rather than directly triggering routing actions.

Yes, you can and should use explicit NavOptions such as launchSingleTop to shape history. Applying these options ensures predictable back-stack behavior and avoids duplicate screen instances during navigation.

Navigation breaks because the approach requires minimal argument passing and typed routes. You must enforce argument discipline by avoiding complex objects and relying on typed parameters in your route model.