Coroutine Scopes - Kotlin Coroutines

🏆 My Online Courses
⭐Discount Coupon: LAUNCH-STEVDZA-SAN
stevdza-san.com
🐱‍👤 Wanna become a member? Join!
/ @stevdzasan
📸 Instagram
/ stevdza_san
Kotlin coroutines provide an API that enables you to write asynchronous code. With Kotlin coroutines, you can define a CoroutineScope, which helps you to manage when your coroutines should run. Each asynchronous operation runs within a particular scope.
Global scope is used to launch top-level coroutines which are operating on the whole application lifetime and are not cancelled prematurely.
A LifecycleScope is defined for each Lifecycle object. Any coroutine launched in this scope is canceled when the Lifecycle is destroyed.
A ViewModelScope is defined for each ViewModel in your app. Any coroutine launched in this scope is automatically canceled if the ViewModel is cleared. Coroutines are useful here for when you have work that needs to be done only if the ViewModel is active. For example, if you are computing some data for a layout, you should scope the work to the ViewModel so that if the ViewModel is cleared, the work is canceled automatically to avoid consuming resources.
implementation "androidx.lifecycle:lifecycle-runtime-ktx:2.2.0"
implementation "androidx.lifecycle:lifecycle-viewmodel-ktx:2.2.0"
Other videos:
The Basics - • The Basics - Kotlin Co...
Jobs & Cancellation - • Jobs and Cancellation ...
runBlocking - • runBlocking - Kotlin C...
withContext - • withContext() - Kotlin...
🕒Timestamps:
0:00 - Introduction
3:00 - Create Coroutine Scope
7:50 - GlobalScope
10:47 - lifecycleScope & viewModelScope

[@duncanmoiyo6069]

You've significantly simplified the comprehension of coroutine scopes. I truly appreciate it.

[@kristofs8893]

I had no chance of understanding Coroutines, but you made it look so simple!

[@StevdzaSan]

Yay, happy to hear that buddy!

[@Axelfromthehudjelud]

Ok, this is the best explanation of the things that were confusing me. Thank you very much!

[@100rabhGrwal]

Thankyou dear for this easy and understandable explanation 👍

[@adrienchew]

Thank you for all the good content!

[@TheDamiankain]

It amazes me how quickly and easily this topic can be explained and shown !!!

[@kmcgill88]

Thanks!

[@StevdzaSan]

Thank you! ❤

[@ashwin_mahajan]

Very well explained and demonstrated, thank you. 🙌

[@kwesiamartey]

That is my man never disappoint, You are the best

[@adwatt357]

Loved your explanation style !! Keep up the good work !!

[@stasleonov5196]

It is amazing! I finally understand what happen when we use lifecyclescope

[@shadiossaili7377]

Yes please do more videos like this!

[@TheInvisibleWasTaken]

You are amazing. Thanks for the content.

[@nesibeyyubov554]

best explanation ever, thanks too much

[@vaibhavarora8793]

Thank You , It was very useful.

[@Another0neTime]

The best!

[@michaelappiah-kubi2829]

Thank you

[@slobom.6744]

Great Explanation, thanks bro

[@Mkumarei]

Thank you ...

[@nicolasvantsis6166]

Very nice

[@anudeepananth]

So there is no way to use a LifecycleScope or ViewModelScope inside of an Adapter class?

[@giorgikakhetelidze2115]

What is difference between CoroutineScope and GLobalScope about their lifcecycles? when CoroutineScope Cancells autmatically?

[@pavelgera72]

хорошие видео для понимания

[@turtle733]

+1 thank you :)

[@ajayvamsee7508]

So you mention global scope coroutine will run even fragment A is destroyed but after again come back to fragment A the fragment A will start again right then coroutine will start again.. So we have 2 coroutines or what will happens..?

[@pinoy_marites_beh]

what if you created an infinite loop without using "delay" and instead system time difference, I think it will not be cancelled even if the coroutine is tied to the lifecycle.

[@sumit180288]

Make a detailed video on Coroutine Jobs

[@baur22]

Will there be a jetpack compose course?

[@StevdzaSan]

Definitely in the future

[@roushanali1918]

I like this... but want to know is there any better content for proffessionals?

[@nileshdhawale2138]

When u create video use android studio default theme, it will be very clear for visibility as compare to dracula theme