shared-viewmodels

To share ViewModels in KMM, you encapsulate a three-part contract exposing state via StateFlow, events via a Channel, and a single onAction entry point. This canonical pattern is consumed directly by Jetpack Compose and SwiftUI.

Managing UI state with StateFlow in KMM requires a shared ViewModel that enforces non-null initial state and delegates business logic to use cases. This ensures platform-appropriate error handling and reduces divergence between Android and iOS.

Yes, you can use a single onAction entry point in a KMM ViewModel to handle UI actions across both Jetpack Compose and SwiftUI. This centralizes action processing and reduces boilerplate in your platform-specific UI layers.

To handle UI events in a shared KMM ViewModel, you expose a Channel-based events stream alongside your StateFlow state. This ensures events are managed appropriately and consumed consistently across Android and iOS implementations.

Yes, the shared ViewModel pattern enforces non-null initial state to ensure both SwiftUI and Jetpack Compose receive valid data immediately upon subscription. This requirement prevents null-related rendering issues across platforms.

The limitation of this three-part contract is that it requires strict adherence to delegating business logic to use cases and managing domain-specific error types. This architectural enforcement may increase initial setup complexity for simple KMM applications.