Prepare your project for KMM

Kotlin Multiplatform is not yet stable. Despite this, many companies have taken the leap of faith and have started adopting it in their production projects.

In this session, we will see an overview about KMM (Kotlin Multiplatform Mobile) and how to prepare your project to adopt it.

A deep look at the modularization architecture and how it facilitates sharing the maximum layers between the different stacks.

We will make the focus on Android and iOS, specially coming from native projects. We will explain how to migrate your project in order to integrate it with a KMM module. Lastly, we can not forget that we can use the shared modules on Desktop and Web Apps.

Will you take the leap of faith?

Transcript

1. @oussamto Prepare your project for KMM 1
2. @oussamto Oussama Ben Wafi @oussamto benwafi.o@sfeir.com Senior Developer @ SFEIR 2
3. Introduction 3
4. @oussamto • KMM not already stable, things may change • Architecture still subjective topic 😉 Disclaimer
5. @oussamto 5 • KMM overview • How? application in from scratch project • How? existing project (monolithic,Modular…) • Implementation • KMM Librairies What to expect
6. KMM ? 6 • What ? • Why ? • How ?
7. KMM?
8. Kotlin
9. Shared Module (platform-specific)? expect class Platform() { val platform: String } actual class Platform actual constructor () { actual val platform: String = "Android ${android.os.Build.VERSION. SDK_INT}" } actual class Platform actual constructor () { actual val platform: String = UIDevice. currentDevice.systemName() + " " + UIDevice.currentDevice.systemVersion } commonMain androidMain iosMain
10. How 10 • From scratch • Monolithic app • Basic-modular by layers • Modular by feature
11. From Scratch Project Android App iOS App Shared module ViewModel Jetpack Compose ViewModel SwiftUI UseCase UseCase Repository Repository LocalDataSource RemoteDataSource ApiService Database
12. Monolithic App app
13. Basic-Modular app • Domain can go shared • Data looks monolothic, we can find a many dependencies • Core looks monolithic, coreDesign, data-network data domain UI core
14. Modular by feature app app data-Network shared data-database shared PaymentShared data domain PaymentUI DashboardShared data domain DashboardUI Shared Core
15. What to share? Jetpack Compose SwiftUI ViewModel ViewModel UseCase Repository RemoteData Source LocalDataSo urce ApiService Retrofit Alamofire Database Room Realm Ktor SqlDelight
16. DI : Shared interface RemoteData Source Interface ApiService ApiServiceImpl Retrofit ApiServiceImpl Alamofire
17. Modularizing data data network datastore data-test data-base
18. Modularizing libraries domain data UI Logger
19. Modularization Benefits 1. Faster 2. Good For business 3. Easy and scalable development 4. New technology experiment 5. Simple and easy to test
20. Implementation 20
21. Home UI Android Module
22. Shared-Core Module
23. Shared-data-network Module (1/4)
24. Shared-data-network Module (2/4)
25. Shared-data-network Module (3/4)
26. Shared-data-network Module (4/4)
27. Shared module
28. Shred module dependencies
29. Android app dependencies dependencies { implementation project(path: ':homeUi') implementation project(path: ':shared') implementation project(path: ':data-network-shared') • Separate the UI Module • Make Domain and Data module into shared module • Extract data-networking into shared module
30. iOS dependencies iOS app will depends on shared module which includes • shared-core • data-network-shared
31. Sharing is Caring 31 • Most useful libraries • Conclusion
32. @oussamto Most useful libraries • xcode-kotlin: Xcode plugin for Kotlin debugging and source formatting • Ktor: Client/Server networking • Kotlinx.Coroutines: Support library for coroutines. • Kotlinx.Serialization: Complete multiplatform support: JVM, JS and Native. • SqlDelight: Multiplatform SQLite model facilitation library.
33. @oussamto Dependency injection
34. @oussamto Api Keys ?
35. @oussamto Resources ?
36. @oussamto sealed class/Interface
37. @oussamto Kermit the log Kermit is a Kotlin Multiplatform logging utility with composable log outputs. Out of the box, the library defaults to platform-specific loggers such as Logcat and OSLog, but is easy to extend and configure. Logging
38. @oussamto • Start small • Think together • Think modularization • Join KMM community Conclusion
39. @oussamto Oussama Ben Wafi @oussamto benwafi.o@sfeir.com Thank You 39
40. References • https://kotlinlang.org/docs/ • https://github.com/android/nowinandroid • https://touchlab.co/