Navigation Mistake In Jetpack Compose

In this video, you'll learn about how to not make an often encountered navigation mistake in Jetpack Compose
Let's connect 🤗:
/ daniel-atitienei
Blog: / daniel.atitienei
Do you like my content? Here you can buy me a coffee ☕:
www.buymeacoffee.com/danielat...

[@SunAndMoon-zc9vd]

It is nice to see the solution, but I would also have liked to hear more about what exactly lines 105 and on mean :)

[@daniel.atitienei]

When you press on the back button the app lifecycle changes. That line checks if the app lifecycle is RESUMED. RESUMED means that the app is now focused and the user can interact with the app.

[@vengateshm2122]

Useful tip.

[@daniel.atitienei]

Glad it was helpful!

[@vengateshm2122]

@@daniel.atitienei Same can be used while navigating to other screen also.

[@muhammadhassaan1990]

in this case, why you won’t use navigateUp() instead of popBackStack() for Back button?

[@muhammadhassaan1990]

simple solution, isn’t it ?

[@raja_uma1r]

Then you won't be watching this video if he did that! Lol

[@daniel.atitienei]

Didn't know about that 😅

[@vijaya5171]

How does it differ from launchSingleTop in navigation from screen 1 to screen 2 if we press screen 1 button multiple times?

[@daniel.atitienei]

I think it will open only once the screen 2, but if you navigate back by pressing multiple times it should have the same behaviour.

[@adagabranca]

I'm pretty sure navigation has something called popUpTo and popUpToInclusive that resolves the matter no ?

[@daniel.atitienei]

No because that is used when you navigate to a next screen to remove the previous one from back stack.