Demonstrate methods to contribute concrete Swift implementations to the KI dependency graph

[JessalynWang]

Currently in non-direct integration of KMP and iOS it is not exactly clear how to create and connect concrete Swift implementations of a Kotlin interface. There are multiple ways to do this. We should create a recipe to demonstrate how it can be done. We should also demonstrate out how to do this with metro eventually, keeping it to KI for now

[tudorluca]

@JessalynWang apologies for the off-topic message here, but I saw your talk at KotlinConf & really loved it. congrats!

also, are the slides somewhere online?

[JessalynWang]

Hello, thanks for coming to the talk! I've uploaded the slides here: https://speakerdeck.com/jessalyn/expedited-shipping-accelerating-ios-development-with-kmp-at-amazon. Please don't hesitate to reach out if you have any questions or comments

[tudorluca]

We're starting a new project and we'll try to use app-platform (if not as a direct dependency, at least in mind-set & borrowed ideas). In the past we've successfully shipped apps with Square's workflow-kotlin and Slack's Circuit, but for this new project we're looking to have a single "mobile team" in code & spirit.

We are strong believers in KMP, "compiler-guaranteed DI graphs", native UIs and "navigation is business logic". The big pain-point in all this is SwiftUI and the patterns its pushing devs towards (muddling view & navigation concerns), so this will be the biggest rough edge for which I might reach out for advice. 🙏

Maybe it'll be worth enabling the "Discussions" tab on github or a dedicated slack channel on kotlinlang?

@JessalynWang thanks for the slides & keep up the great work! 🫡

[JessalynWang]

I've enabled discussions for now. You can find me in kotlinlang if you'd like, but I don't think we need to make a channel there at this time