Writing Swift-Friendly Kotlin Multiplatform APIs — Part I: Intro
<p>Kotlin Multi-Platform Mobile (KMM) is awesome… for Android developers. Using or coding a KMM library is not much different from using a regular Kotlin library like Jetpack Compose, OkHttp, and whatnot. However, for iOS developers, the story can be different. Therefore, it is essential to get them on board for the success of your KMM library.</p>
<blockquote>
<p>This article is part of a series, see the other articles <a href="https://medium.com/@aoriani/list/writing-swiftfriendly-kotlin-multiplatform-apis-c51c2b317fce" rel="noopener">here</a></p>
</blockquote>
<p>Although <a href="https://www.kodeco.com/6754-a-comparison-of-swift-and-kotlin-languages" rel="noopener ugc nofollow" target="_blank">Swift has many similarities with Kotlin</a>, it was built to replace Objective-C. As a result, it has many of its quirks, like the lack of proper namespacing. Consequently, a few Kotlin features will be like the Portuguese word <a href="https://www.npr.org/sections/altlatino/2014/02/28/282552613/saudade-an-untranslatable-undeniably-potent-word" rel="noopener ugc nofollow" target="_blank">“<em>saudade</em>”</a>: they have no direct translation in Swift. Using them can produce useless or cumbersome APIs for your iOS teammates. This series of articles aims to help you identify those problems and provide solutions for the most common ones.</p>
<p><a href="https://betterprogramming.pub/writing-swift-friendly-kotlin-multiplatform-apis-part-i-1173ec405a20"><strong>Visit Now</strong></a></p>