Pokémon Detail Screen (1) - MVVM Pokédex App With Jetpack Compose - Part 7

In this video we will start to implement the PokemonDetailScreen.

⭐ Get certificates for your future job
⭐ Save countless hours of time
⭐ 100% money back guarantee for 30 days
⭐ Become a professional Android developer now:

Get the source code for this video here:

[matt-g-recovers]

Man, Compose is pretty sweet Phillipp.
Great tutorial here as well.

[mrtruthvirtue]

Thanks for the tutorial, your're such the best amazing mobile developer I've ever know as far.

[MrMayur]

Thanks a lot. I have a question. Regarding the screen management. How are we supposed to manage screens in jetpack compose. Will there be only one activity and Other screens will be just composables?

[Mikes-Code]

Hey, can we pass entire object as arguments to the navigation, or do we have to use primitives? (Int, String)

[mehulbisht]

Not actually related to compose but shared ViewModel. Let's suppose you open a Pokemon details fragment, press back and then open it again. In case you want to keep a track if this fragment was opened for the very first time or not (only consider while app was in memory, not persistence with Jetpack datastore), do you use a sharedViewModel to Keep a track of this event? or Is there a better way to persist in memory data? For my use case, I want to know if user was already on the fragment or navigated to it using navigation drawer, since loading data when navigation drawer is animating causes a UI lag.