Kotlin-Multiplatform-Libraries VS kotlin-flow-extensions

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

I don't know, why I'm downvoted here, but it is very relevant if the library provide the operators you need or if you have to implement them yourself. If Kotlin Flow is enough, then use it. From experience you don't have to go to far to miss operators from Reactor or RxJava. Maybe some day additional libraries like https://github.com/akarnokd/kotlin-flow-extensions will fill the gap, but for the time being Reactor or RxJava offer a lot more for (not trivial) real world use cases.

Why do you want to keep Flow such a small library? It could be an attractive alternative to RxJava or Reactor, but it misses many useful operators today. On the other hand it brings a lot more operatores than would be required as a foundation for other frameworks (likeKotlin Flow Extensions). From my point of view Flow stays in the middleground with no good reason.