Lifecycle events in Jetpack Compose!

Compose is awesome, but we did lose some clarity around traditional lifecycle events our Activities and Fragments go through. Follow along as I show you a simple way to listen for these events and do certain actions like make a network call!
Don't forget to subscribe and enable notifications to stay up-to-date!
Docs: developer.andr...
Source code here: github.com/the...
Full playlist here: • Season 11: Jetpack Com...
Jetpack Compose Basics: developer.andr...
=========== Popular Series ===========
Redux e-commerce app: • Season 10: E-commerce ...
Rick and Morty app: • Season 6: Rick & Morty...
=========== Connect with me ===========
LinkedIn: / domenic-polidoro-802b72b4
Instagram: / dom_polidoro
Twitter: / developer_dom
Tiktok: / building_android

[@dadveloper2326]

Important to know in case there are things that Compose isn't just taking care of, like it does so often! We must never forget our roots!!

[@TheAndroidFactory]

Oh for sure. This effect is especially helpful for hybrid projects that still leverage Activities and Fragments, but have the UI layer in Compose!

[@dadveloper2326]

@@TheAndroidFactory Yes definitely! hadn't thought of that!

[@pigua7705]

The course helped me a lot, thank you for your efforts

[@TheAndroidFactory]

Woo! Thanks for watching, glad it helped :)

[@soontaek]

Thank you. I subbed :D

[@TheAndroidFactory]

Hey happy it helped :)

[@TheAndroidFactory]

Thanks for the support!

[@rahulchandrabhan]

Nice one

[@TheAndroidFactory]

Thank you!

[@ubersticks]

The performOnLifecycle() is an interesting way to handle this. Is there a reason to favor that over LaunchedEffect(Unit) { viewModel.fetchQuoteOfTheDay() } ??

[@TheAndroidFactory]

Great question -- from what I understand the LaunchedEffect is a tiny bit more limiting. The performOnLifecycle idea enables the code to hook into different traditional lifecycle events like we would normally have available to us in Fragments. So, for instance, I don't believe LaunchedEffect would run again if you background the app and bring the app into the foreground again, whereas the performOnLifecycle would inside the `onResume` lambda. So, in this implementation, we are refreshing the quote of the day any time the Activity is resumed. They both are useful tools and, in this case, I think either approach is fine! Let me know your thoughts