Curious to get a show of hands here; but in my 3 m...

# swift-export

[darkmoon_uk]

Curious to get a show of hands here; but in my 3 most recent Kotlin Multiplatform projects featuring iOS; the only Swift Interop challenge I face is Importing Swift-only API's to Kotlin, and not Exporting Kotlin to Swift, as was prioritised on the roadmap 🤔

While K Compose Multiplatform is certainly not the only way to use KMP, as a major part of the ecosystem it promotes minimising the amount of Swift in the whole project and maximising Kotlin - that would indicate import-first as priority.

❗ More critically, the new iOS API's are Swift only which means I've had to write a significant number of ObC/Swift wrappers to use the features I need in KMP. This is tolerable - but only just in some cases 🥴 - and does beg the question: Why did KMP team focus on Export over Import, where only Import has ever been an issue for me - is it a technically necessary first step? More achievable? Or is my 'import case' the unusual one (finding this hard to believe) alphabet white question

As a repeated Kotlin/iOS user, I'd like to understand if/when we can expect direct Swift *Import*; which seems far more valuable than Export to me.

To be specific: ProximityReader, FamilyControls and DeviceActivityMonitor have been the newer, Swift-only API's I've needed to wrap.
Thread in Slack Conversation