You're reading from Simplifying Application Development with Kotlin Multiplatform Mobile Write robust native applications for iOS and Android efficiently

Product type Paperback

Published in Mar 2022

Publisher Packt

ISBN-13 9781801812580

Length 184 pages

Edition 1st Edition

Languages

Kotlin

Tools

Android

Concepts

Application Development

Author (1):

Robert Nagy

View More author details

Table of Contents (15) Chapters

Preface

1. Section 1 - Getting Started with Multiplatform Mobile Development Using Kotlin

2. Chapter 1: The Battle Between Native, Cross-Platform, and Multiplatform FREE CHAPTER

3. Chapter 2: Exploring the Three Compilers of Kotlin Multiplatform

4. Chapter 3: Introducing Kotlin for Swift Developers

5. Section 2 - Code Sharing between Android and iOS

6. Chapter 4: Introducing the KMM Learning Project

7. Chapter 5: Writing Shared Code

8. Chapter 6: Writing the Android Consumer App

9. Chapter 7: Writing an iOS Consumer App

10. Section 3 - Supercharging Yourself for the Next Steps

11. Chapter 8: Exploring Tips and Best Practices

12. Chapter 9: Integrating KMM into Existing Android and iOS Apps

13. Chapter 10: Summary and Your Next Steps

14. Other Books You May Enjoy

Deciding on a mono repository or a shared library

In this section, we're going to reason about the pros and cons of the following two repository setups:

Mono Repository: This is where the shared code is just a module/submodule. This is the choice of most KMM/KMP example projects.
Multiple Repositories: This is where the shared code is like a library that's consumed by the different platforms; that is, Android and iOS. Most production apps will likely see this option as more attractive.

Let's start by looking at mono repositories.

Mono repository

In a mono repository structure, your shared code, the Android app, and the iOS app are all contained in the same repository, as shown in the following diagram:

Figure 9.1 – Mono repository

Some of the KMP examples out there, such as the ones where code is shared not just between the different frontend applications but in a server-client/backend-frontend mode, could inspire...