How does your KMP app connect StateFlow to SwiftUI?

[sonmbol]

I would like to understand the integration patterns KMP teams use today.

Are you using:

• a manual Swift ObservableObject adapter per screen;
• SKIE AsyncSequence support;
• KMP-NativeCoroutines;
• callbacks or CFlow wrappers;
• another library;
• direct Observation integration?

What has been the hardest part: lifecycle ownership, cancellation, child ViewModels, errors, generated APIs, or SwiftUI invalidation? Real examples will guide the 1.1 roadmap.

[Alox1d]

A concrete state-shape example from my KMP library may be useful for the roadmap, although I don't have a shipped SwiftUI bridge to report.

DateParser Kotlin returns immutable matches with an instant, timezone, and optional range end/recurrence. In a reminder editor, I'd want one observable draft state containing the current input, proposal and manual corrections. An update should not expose a new start time with an old range end, and a view recreation should not replace a user's corrected time with an earlier proposal.

That gives an adapter a bounded test: explicit time -> unresolved time -> manual correction -> view unsubscribe/resubscribe, with the reference clock fixed. The shared-code demo supplies the parsing side; its existing UI is Android Compose. If it helps as a small interoperability test subject, a star would be welcome.