Android와 iOS에서 Flow 수집

Your shared code exposes a Flow, but each platform consumes it differently. The trick is collecting that one stream natively on Android and on iOS.

On Android, Jetpack Compose turns a Flow into state with collectAsState. Your composable redraws automatically whenever a new value arrives.

Prefer collectAsStateWithLifecycle so collection pauses when the screen is in the background. It saves battery and avoids needless work.

Plain Flow does not bridge to Swift, because collect is a suspend call. Swift needs a callback-friendly wrapper instead.

A common fix is a small wrapper that subscribes and returns a cancel handle. iOS calls a closure on each value and stops when done.

The wrapper launches collection inside a CoroutineScope it owns. Closing the handle cancels that scope so nothing leaks after the screen is gone.

From SwiftUI you call the wrapper in onAppear, push each value into an ObservableObject, and cancel in onDisappear.

Tools like SKIE generate Swift-friendly Flow APIs for you, so iOS devs collect with native async sequences and skip hand-written wrappers.

However you bridge, make sure collection cancels when the screen disappears. An orphaned collector keeps running and quietly wastes resources.

Notice the pattern: only the thin collection layer is per platform. The data, operators, and state all stay in shared code where they belong. 🤝

Both apps now react to the identical stream, yet each uses its native UI toolkit. That balance is exactly what KMP is built for.

You collected one shared stream two ways: Compose with collectAsStateWithLifecycle, and SwiftUI through a wrapper or SKIE. Shared logic, native UI. 🤝