Kotlin-Multiplatform-Libraries VS Decompose

There's nothing you can do. However, Kotlin's official provides several libraries, so the scope that can be achieved using them is by no means small. Also, AAkira/Kotlin-Multiplatform-Libraries introduces several famous libraries created with Kotlin Multiplatform, which can be helpful. However, it can be quite disappointing when certain environments are not supported. But let's think of it as an opportunity! Let's become the first person to implement it!

Now if you're just writing a crud app (what my hobby project is) and you use compose multiplatform for your UI, SQLDelight for persistence, and one of the many MPP architecture libraries, you don't have to write a wrapper.

We did encounter some problems as a result of our ignorance. When we started on the project, there was very little information on the implementation of KMM, so we had to solve all of the issues ourselves. The Kotlin Multiplatform community is growing rapidly with more articles and reports appearing at conferences and meetups. There are channels in Slack and Telegram, libraries for Kotlin Multiplatform, and so on, plenty of information sources available.

From https://github.com/AAkira/Kotlin-Multiplatform-Libraries#cipher: https://github.com/korlibs/krypto https://github.com/ionspin/kotlin-multiplatform-libsodium

There is a fair selection of libs listed here: Kotlin-Multiplatform-Libraries If you need some deeper insights drop me a DM

Different UI technologies have their own unique features, such as DataBind for XAML (WPF/UWP/WinRT), and more and more UI technologies using Turing-complete programming languages as DSL, such as Flutter (Dart), Swift UI (Swift) and Compose (Kotlin), which can only be said to have advantages and disadvantages. But don't dismiss it out of hand. For Compose, there is a Decompose framework that helps you to separate UI code from business code.

I found this one from badoo. But it seems to be overly complicated.