Book Image

Simplifying Application Development with Kotlin Multiplatform Mobile

By : Róbert Nagy
Book Image

Simplifying Application Development with Kotlin Multiplatform Mobile

By: Róbert Nagy

Overview of this book

Sharing code between platforms can help developers gain a competitive edge, and Kotlin Multiplatform Mobile (KMM) offers a sensible way to do it. KMM helps mobile teams share code between Android and iOS in a flexible way, leaving room for native development. The book begins by helping you to gain a clear understanding of the Kotlin Multiplatform approach, how it works, and how it is different from cross-platform technologies, such as React Native and Flutter, and code sharing options, such as C++. You'll then see how your team can use this software development kit (SDK) to build native applications more effectively by learning timeless concepts and working through practical examples. As you advance, you'll get to grips with the core concepts, understand why UI sharing fails, and get hands-on with developing a small KMM application. Finally, you'll discover expert tips and best practices, along with production- and adoption-related questions, that will help you take the next step in your project and career. By the end of this Kotlin book, you'll have gained a solid understanding of the capabilities of KMM and be able to share code between Android and iOS flexibly.
Table of Contents (15 chapters)
Section 1 - Getting Started with Multiplatform Mobile Development Using Kotlin
Section 2 - Code Sharing between Android and iOS
Section 3 - Supercharging Yourself for the Next Steps

Learning some adoption tips

Have you decided that KMP is for you and your team and would like to try it out? Here are a couple of quick tips to help you mitigate risk and gradually descend into the KMP world:

  • Kotlin/JVM is already used widely for Android development, which you can leverage. You can start by using Android while you introduce platform-agnostic concepts and isolate components that shouldn't depend on the Android framework.

Many teams already do this by having Java/Kotlin modules for their business logic. These teams are already one step closer to making these modules shareable and doing this doesn't need any KMP expertise and doesn't introduce KMP specific risks.

  • You can then start educating your Android team on KMP and gradually make your components platform-agnostic. Make sure that iOS is involved in the communication as they will be one of the consumers of the shared code. I'd encourage iOS people to learn about KMP and contribute...