Pass a Parcelable Object with Navigation Compose | 2 Different Approaches

Very helpful tutorial, works smoothly, second way is better than using Parcelable, in my opinion!

thanks

The second way seems good but im wondering what happens if you have multiple events, and fields in each screen? Wouldn't the view model become too big and unmaintainable ?

What do you think about compose destinations library , is it reliable ?

How would you use the result in the detail screen ( to set values of textfields)?

can you share source code ?

How to show that Object passed in the DetailsScreen ?Gracias.

Really I was searching for a solution for this issue a long time ago, Thanks a lot Stevdza-San for your efforts in Jetpack Compose.

From what I have read, you should NEVER pass in a viewModel to composable functions. Instead, you should obtain them inside the composable function. Secondly, a shared viewModel I guess has to be managed wisely. Are you not better off using SavedStateHandle, that is supplied to all ViewModels? this has a key value pair

The second way is the best one. Thank you very much for your video!

you're the best of the best :)

Is there a GitHub repo with this code?

Great tutorial, straight forward, easy to understand, thank you

That was really informative.
Ty Stev

Hello there, can you create a tutorial on how we can add mongodb realm with sync, using compose,
No much resources for it, your teaching is really good

Why do android libraries and methods keep changing? It's a lot frustrating to learn new ways every month,

Great content, if you can provide a full explain of using a viewModel to manage the state of the composable.

Will you make a course on building multi module app?

I am find another approach like convert object To Json !! is this way correct ?

I guess a shared viewModel is the best way to share data across composables. any memory issues though if we use shared viewModels instead of passing a parceable ?

Using SharedViewModel is a good universal approach. Thanks for the idea and example!

If I have two screens with complex logic or are in different modules, what should I do with the viewmodel? Create another shared module for the viewmodel? Let Google go to hell with their viewmodel! A shame! The proposed data transfer method in Compose is complete crap. Why couldn't the data transfer be done normally? Shared viewmodel is evil!

Please make tuts on realmsync

if I want to make a search app by category, I have to make them parcelable or otherwise?

Thanks a lot for this!!
Great content