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

Exploring Kotlin's core features

Kotlin is an object-oriented programming (OOP) language with many functional programming features. In this section, we'll go over its main features so that you have a basic understanding of how to express yourself in Kotlin later on. Throughout this chapter, we'll be comparing Kotlin to Swift in terms of these core concepts.

Null safety

Having null references in code proved to be an underestimated factor of error proneness in older languages, such as Java and Objective-C (Obj-C), thus it has probably earned its billion-dollar mistake tag (

The purpose and solution are pretty much similar in Kotlin and Swift, with slight syntax and naming differences. They both aim to provide a type system that eliminates the danger of null references. Swift introduced optional types, which can be found as nullables in Kotlin.

Let's see some code in action, in order to...