The last part of the series contains code statistics, shows what problems I've encountered along the way and at the end I share my opinion on Kotlin Multiplatform
This part explains how Kotlin Multiplatform can share code between platforms. Additionally the architecture of the client platform (Web app and Android) is also shown.
Currently, I'm working on a Jetpack Compose Android app which amongst other things allows the user to start multiple stopwatches.
This is the first part where I show a simplified version of the implementation which will only handle one stopwatch. The second part will include the full implementation
Adding flavor dependent features on a shared screen can be troublesome. The problem gets even worse when you don't want to couple app flavors to features they don't use