kotlin-multiplatform-libsodium VS Decompose

Android (Google play store): https://play.google.com/store/apps/details?id=com.ionspin.me...

We also have a iOS build for testing through TestFlight available on this link: https://testflight.apple.com/join/ohRS4Pd4

You can learn more about mementō and the company here http://www.ionspin.com

If you want to share your feedback directly with us you can send it to [email protected], it'll get forwarded directly to all of our inboxes.

I'll also be here for a couple of hours to answer all of your questions.

Ugi

[1] Kotlin wrapped libsodium - https://github.com/ionspin/kotlin-multiplatform-libsodium

You can find the library here: https://github.com/ionspin/kotlin-multiplatform-libsodium

I use Decompose, although I also have a kmp project which that supports. I find the compose extensions providing a very easy API when integrating with compose.

For one of our apps we used https://arkivanov.github.io/Decompose/ for navigation. It is mentioned in the Compose Multiplatform repo, but we found it pretty obscure to use and it has some confusing concepts built in.

View model is Googles recommended approach, but there are other approaches out their you can use like decompose

When you are building your app in KMM, sometimes you need to pack some libraries along with project files in the shared module. For example if you are using Decompose you need to access it's Value class in Swift.

I don't have much experience with conductor, so I'm curious what your concerns about lifecycle is lacking compared to fragments? But if your team already knows that framework I might just stick with views over fragments. I see there is a compose integration if you do ever plan on picking that up with conductor. Otherwise compose makes fragments obsolete and your team already knows conductor. I do agree the navigation story in compose is not mature especially after jetpack compose navigation. But there are other 3rd party libraries like compose destinations or decompose, but would be nice to see something better 1st party.

I personally like decompose for its testability, clear separation of concerns, and apis for compose animations. Plus it's multiplatform so you can use it for other kmp targets.

Full discretion, all my new apps are built using mvi with MVIKotlin and decompose for the compose extensions for navigation animations. A sample project I have built with that architecture can be found here.

Check out Decompose, it's multiplatform - https://github.com/arkivanov/Decompose

Decompose