simple-stack VS Decompose

As someone who had been using single-activity since 2015 (a'la Flow) and eventually just rewrote the whole thing to fix all the bugs we had with it in 2017, I find it sad that the single-activity approach was questioned not because it was harder, but because people made their own lives harder. And then Google made their lives harder.

I've been using single-activity but with Simple-Stack since 2016 and never deprecated it because Navigation just has these quirks that impede you a lot. I know how to use it but wouldn't really pick it.

This is why we've been using https://github.com/Zhuinden/simple-stack and it was never deprecated. We've been using it for 6 years, I'd say there was a critical bug but it was fixed in 2.3.1...

I mean, we use Simple-Stack because it makes things easier, if it didn't we'd have ditched it long ago https://github.com/Zhuinden/simple-stack

Agreed. I also added support for it 2 weeks ago.

I don't, because we use this and it's better than activities+intents 😅

We've been making single activity apps with https://github.com/Zhuinden/simple-stack and it has been easier than multi-activity.

I still use https://github.com/Zhuinden/simple-stack to this day, although I still use it with fragments.

I have been using Fragments instead of compound viewgroups lately with simple-stack as the navigator for the single-activity, although I need to figure out how to switch to use onBackPressed+onBackInvokedCallback and not just onBackPressed.

You can think of Simple-Stack as a direct successor of Mortar+Flow.

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