Decompose VS ktor

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

In paralel Jetbrains has created a lot of KMP frameworks that are awesome. One of them is Ktor that helps "create asynchronous client and server applications."

Ktor, a powerful web framework built with Kotlin, offers a lightweight and flexible solution for building web applications. In this article, we will guide you through the process of creating a Ktor project manually using Gradle and SDKMAN!. By following the steps below, you'll have a basic Ktor project up and running in no time.

take a look at http4k and ktor for Kotlin specific frameworks Spring has first class support for Kotlin e.g. the following will give you reactive HTTP endpoints when using spring-webflux (this is what is use at work):

Ktor (Microservices framework by JetBrains)

For Android you should use a more mobile friendly framework like Retrofit or if you use Kotlin you can use the multi-platform Ktor library with it's client module

And last but not least, Ktor Client as our HTTP client. https://ktor.io/ It's a pretty amazing http client library and integrates well with Kotlinx serialization and Coroutines.

Kotlin is going to be great with almost every single JVM server. Spring works well with Kotlin, and is directly supported, but spring is also massive, very bloated. I recommend looking at https://github.com/ktorio/ktor which continues to serve all of my needs very well, integrates fantastically with Kotlin coroutines, and has very fast startup time and very good performance.

For the sake of the test, we use Ktor - the easiest way to do so is to use initializer.

I know you are looking for Spring Boot and/or Quarkus, but have you tried ktor. Just curios if you had a particular reason for choosing the other 2. Disclaimer: I haven't used ktor.