# Livestream: Close the Swift/Kotlin Platform Gap - Touchlab

DevFeed: [Livestream: Close the Swift/Kotlin Platform Gap - Touchlab](<https://devfeed.tech/articles/livestream-close-the-swift-kotlin-platform-gap-touchlab-38173.md>)

Original publisher: [Read original article](<https://touchlab.co/close-the-platform-gap>)

Published: 2024-07-26T00:00:00Z

Content type: tutorial

Language: en

Sources: [Touchlab | Enterprise Mobile Innovation & Development](<https://devfeed.tech/sources/touchlab-enterprise-mobile-innovation-development.md>)

Topics: [Kotlin Multiplatform](<https://devfeed.tech/topics/kotlin-multiplatform.md>), [Swift](<https://devfeed.tech/topics/swift.md>), [multiplatform](<https://devfeed.tech/topics/multiplatform.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>)

Tags: [coroutines](<https://devfeed.tech/tags/coroutines.md>), [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [interop](<https://devfeed.tech/tags/interop.md>), [ios](<https://devfeed.tech/tags/ios.md>), [kmp](<https://devfeed.tech/tags/kmp.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [swift](<https://devfeed.tech/tags/swift.md>), [xcode](<https://devfeed.tech/tags/xcode.md>)

## AI overview

This livestream introduces the Swift/Kotlin platform gap in Kotlin Multiplatform development. It uses a "Bad Swift Simulation" to show how Kotlin APIs can lose modern features when exported to Swift, then discusses tools, best practices, and SKIE for improving Swift interoperability and developer experience.

## Source excerpt

Calling Kotlin Multiplatform from Swift can be a painful experience. Kotlin engineers new to KMP rarely understand the issues. The "Bad Swift Simulation" helps Kotlin engineers "feel the pain" by replicating the experience directly in Kotlin. With that experience, understanding how to fix the situation, and why you need to, is much simpler.