riverpod VS Decompose

From a library standpoint, I would recommend https://riverpod.dev over any other state management libraries for productivity purposes.

I have the following code. When I hot reload I get an error like this. Apparently this is fixed in dart 3 and Remi mentions a solve here. I am unclear how to refactor my code to achieve the solve without upgrading Flutter to an unstable version (which I've tried and cannot use because of certain render issues).

I saw this official example but it doesn't use riverpod_generator : https://github.com/rrousselGit/riverpod/blob/master/examples/todos/lib/todo.dart

Looking at the riverpod.dev docs, I saw that they were using Docusaurus which led me to creating this site. You can think of it as a guide or your go-to when trying to build gRPC servers and clients using Dart. It's open source hosted at this repo and everyone is really invited to Collaborate.

Riverpod Docs

I think you might need to use a state management if you want to keep the username and email always in scope in your application. Consider using riverpod or provider

You're right, it's Riverpod.

Sources: Riverpod: https://riverpod.dev REST: https://github.com/codeReview-youtube/flutter_auth_api PROJECT: https://github.com/codeReview-youtube/flutter_rest_riverpod_authentication

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