Kotlin Coroutines 101 - Android Conference Talks

Manuel Vivo, Android Engineer from the Developer Relations team at Google, gives an introduction to Kotlin Coroutines. Stay tuned to find out about the problems coroutines are trying to solve, how to use coroutines in Android, how to test them, and much more!

#Kotlin #AndroidDev #Featured

[whoadityanawandar]

Feels like trying to understand this is gonna make me forget whatever little android programming I know.

[yamsergey]

Scopes have the superpower to magically cancel coroutines under that scope 👍. Oh wait it won't cancel them automatically 16:35 cancelation requires cooperation 😀

[l_a_h]

This is a helpful video. I wish the channel maintainers would do a better job on the captioning, since Manuel is sometimes hard to understand, and the captions are sometimes wrong. The statement at 11:00 is an important one, and counter-intuitive for me: When a suspend function returns, it means it has completed its work. When you think about it, the only (?) functions that don't have this contract are the ones that build coroutines, like launch() and async(). Right?

[camiloconstante]

16:00 I think it should be ': User = supervisorScope {}' otherwise the function will require a return. Thank you for the video!

[marlonlom]

one of the best 101 videos for coroutines

[crayoncolors]

Very well explained! I noticed advance code lab link is not working

[MikeMitterer]

THE best introduction about coroutines - Thanks

[mahmudiftekharzamil]

Now I understand how to use coroutine. Excellent video. I have one request. Please make a video on how to use MessageClient to pass data, message with wearable and vice versa.

[straykidsco]

👋🏼🇨🇴🙋‍♀️Saludos desde Colombia, 💻📲Kotlin es mi lenguaje favorito con el que yo aplicaciones nativas para Android

[lucye]

Awesome video that really breaks it all down. Great job, thank you!

[hectorantoniotafoyagarcia]

Great content and excelent ppt, I would only add more explanation on the Jobs part because it doesn't really work as described and no further explanation was given on how to manage jobs. Most of the code examples can run the same without specifying the SupervisorJob

[StefanHolodnickDailyinvention]

This is great. It certainly beats the old way of doing asychronous requests.

[alexeys.]

Thank you for this video. It really helps to understand.

[pierrelaurence]

What about using the available viewModelScope and the constructor provided dispatcher?
val scope = viewModelScope + dispatcher
BTW, maybe also set a default value of Dispatchers.Main to the dispatcher, so that ViewModels don't require factories.

[cdmunoz]

Thanks Manuel, such a really good job! Congrats to all Android team
Although I have my concerns when testing coroutines, because we need to take into consideration several scenarios .. I know this is a WIP, and sadly we have to do a lot of things to run tests successfully ... it should be more straight forward. Looking forward to have improvements there, but in the end, coroutines is such a really good tool, really happy for that

[kaustubhpatange]

Most of the things in this video was already explained in io 2019 talks lecture Understanding Coroutines.

[nitinpraksh]

Hello Android Developers,

Really great video about coroutines but I have a question at 7:00 duration you said that execution moved to a different thread but I read many articles they said that when we call a suspended function it will suspend the function from the calling thread until or unless we got the result or error and resume it on the same thread when we got the result.

So my question is, will the coroutine context such as (IO, Main, Default) create a new different thread accordingly where execution going to

[lycheejuicelichigaming]

16:00 in order to use structured concurrency you have to rethrow the CancellationException 😀

[davidespano]

Great work this video is a very useful practical summary, thanks!

[lijulius]

Thanks but it's better to use a voice changed app which can make your speak more clear and easier to understand, especially for those who're not good at English, like me.