![]() ![]() Therefore your app ends up having a more native feeling - at the cost of platform adaptation for the UI. In KMP, you write the business logic once and put it in a shared library, then write your UI using native libraries for each platform you target, such as Jetpack Compose for Android, Swift for iOS, Compose Multiplatform for desktop, etc. This is great for portability but does not easily provide a native UI experience. You can still write some adaptation logic to adapt the UI to the platform but at the end of the day, whether you build it into a mobile, desktop, or web app, your app is rendered through the Flutter engine (built on the Skia graphics library). In Flutter, you write your business logic, your UI, and it can run anywhere. The one I find most interesting is how they handle their cross-platform architecture. There are quite notable differences between Kotlin Multiplatform (KMP) and Flutter, besides the whole Dart vs Kotlin thing. ![]() When combined with Jetpack Compose, this means we now have a way to make an app targeting mobile, desktop, and web using only Kotlin. If you do not know what Compose Multiplatform is yet, here is a TLDR copied directly from JetBrains’ website:įast reactive Desktop and Web UI framework for Kotlin, based on Google’s modern toolkit and brought to you by JetBrains. Kotlin Multiplatform overall principle (source: ) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |