Kotlin Multiplatform, Compose Multiplatform: Apple’s Strategic Failure
<p>“The Kotlin Multiplatform technology is designed to simplify the development of cross-platform projects. It reduces time spent writing and maintaining the same code for different platforms while retaining the flexibility and benefits of native programming.” ~ <a href="https://kotlinlang.org/docs/multiplatform.html" rel="noopener ugc nofollow" target="_blank">Kotlin.org</a></p>
<p>It’s the Holy Grail of mobile application developers — and management — everywhere.</p>
<p>The ability to write code <em>once</em>, and then run it on any platform.</p>
<p>There are several reasons to want this:</p>
<ol>
<li>A common code base reduces inconsistencies between platforms.</li>
<li>Reduced testing requirements.</li>
<li>Reduced time to market.</li>
<li>Reduced cost of development.</li>
</ol>
<p>But to be honest, it’s probably the latter point that’s key.</p>
<p>Because when you get right down to it, mobile application development is expensive. iOS and Android developers are not cheap, and management and the C-suite have always chaffed at the idea of having to spend perfectly good money to write the same exact application twice.</p>
<p>Once for iOS, and once for Android.</p>
<p>Kotlin Multiplatform (KMP) and Compose Multiplatform (CM) represent some of the latest attempts to solve those problems. Together, they envision a bright shining hope for management…</p>
<p>And for Apple, they represent a major, strategic failure of the highest order.</p>
<p><a href="https://betterprogramming.pub/kmp-cm-apples-strategic-failure-cb758c24f824">Visit Now</a></p>