Recapitulating what you have learned
We started this book by reasoning about what market need Kotlin Multiplatform tries to meet. We explored native applications, why people tend to turn to technologies such as React Native and Flutter, and why these technologies may not turn out to be the best solutions, generally speaking.
Furthermore, we discussed how to differentiate multiplatform from cross-platform notions, what a multiplatform technology tries to achieve, and how Kotlin Multiplatform leverages its tech stack to provide a sensible multiplatform solution.
After reading the first two chapters, you are expected to have a broader understanding of which technology is more suitable for a specific use case, project, or client need.
In Chapter 3, Introducing Kotlin for Swift Developers, we made a slight detour to ensure that iOS developers don't feel alienated by Kotlin and that everyone has the necessary knowledge to start learning about Kotlin Multiplatform.