kmp-navigation

Cross-platform navigation in KMP uses shared code patterns bridged to platform-specific implementations. This Skill covers Voyager for unified navigation, Decompose for state management, and platform-native adapters that connect to Compose Navigation on Android and SwiftUI on iOS, with concrete integration examples.

Voyager provides library dependencies and build configuration to enable navigation across Android, iOS, and shared code. This Skill specifies integration steps, required dependencies, and sample navigational code patterns to implement common flows in your KMP setup.

Yes. Decompose manages state and configuration across modules in Kotlin Multiplatform projects. This Skill explains Decompose-style navigation patterns, how they differ from library-based approaches, and when to apply them alongside Voyager or platform-native strategies.

Platform-native bridging connects shared navigation logic to Compose Navigation on Android and SwiftUI on iOS. This Skill provides guidance on implementing consistent navigation flows by adapting shared patterns to each platform's native navigation system.

Voyager offers library-driven navigation across platforms with built-in adapters, while Decompose emphasizes state and configuration management across modules. This Skill covers both approaches, their trade-offs, and how to choose based on your project's architecture needs.

No. This Skill bridges the gap by providing platform adapters and integration patterns that abstract platform-specific details. You define navigation in shared code or Voyager, then adapt it to Compose Navigation and SwiftUI using the patterns and examples included.