Android Code-Along: Kotlin coroutines 

38:25 Execution handling in the repository 40:40 Difference between Blocking and suspending a thread 44:50 Best way to do error handling in coroutines 46:00 suspend function in Dao and Retrofit 49:20 Retrofit and Room safe to call from the main thread 50:56 Any limitations for coroutines? 55:30 Is there a built-in way to retry a suspend function if an error occurs?

Great explanation on coroutines!!! Please do more often this kind of live lessons. Thanks again

Starts at 14:43

This is great! Really really realy great. Please do more of those. And also I would suggest to make more advanced tutorials(like this one or maybe even more advanced), because it is easy to find beginner guides but it is hard to find advanced tutorials

This video helped me a lot to learn about coroutine. This explanation is great.

You guys are the best!!! Can’t express that enough.

fantastic video Android Developers. I crushed the thumbs up on your video. Always keep up the superior work.

Hi, Android Team, please continue this series.

Hi, Please put the subtitles properly while you speak. Actually I am hearing impaired and i am keen to learn Kotlin corountines.

Wow, this is really amazing... Keep this up! I think those code-alongs are really important for some developers to understand topics more deeply and have trouble with written docs (like me sometimes :P)

Please Make a updated video about Paging Library !!

24:09 About the difference between sleep() and delay(), since the Dispatcher uses a thread pool, wouldn't it mean that using delay() , it won't really execute the code after that right away? The reason: The other threads might still working, so there won't be any free thread in the thread pool. Using sleep() prevents it, because the thread is still on the current code, not going to do anything else. As soon as the timeout of the 1 second is finished, it should resume its work.

Very helpful and happy to learn from experts. Looking for more such live explanation videos.

For sure this is more helpful than any other type of resource .

The "Spinner" is not a spinner, it looks like a spinner, behaves like a spinner, but is named "ProgressBar" for some funny really old reason :D Great Video

Great Explanation 👍

really helpful to understand coroutines

Love this format! Thanks for putting this on 🙂👍👍

Live lessons are awesome

It wasn't so obvious to me how you started "calling network requests from the main thread" at 49:33. I mistakenly interpreted that as "making a network request on the main thread". The key concept I had to understand is that the change made to the Retrofit fetchNextTitle() method (making it a suspend function that only returns a String) at 47:05 makes Retrofit *automagically* execute that request on a background thread.

Excellent. Really Good explanation

Very helpful session.. good work guys

Hello World!!!!! Love these lives. I could not see it live.

Closed caption/subtitle is not showing as video, I see there is a lot of delay in caption and video ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-FWxeDqM_WIU.html

Thank you very much.

love this video

how did i not know this?

make more such videos

Good should offical allounce java also offical language as like kotlin. Java and kotlin both should be official language for Android because so many developer java with Android. Android use java platform independent and byte code feature that is why java must be offical language for Android. Good should take over oracle because of java(JSE, JEE, JME). Java mostly use for develop enterprise application.

Ok

wow i have just seen magic unfold here, humans are animals with special gifts

A little bit about limitations 1. It's very bad idea to use coroutines with a code that tries to ensure you do some calls in a same thread. The classic example is DB transactions implementation. You may have a case when the first DB write been invoked in poll_thread_1 and some other call in pool_thread_2. If transaction implementation have something like ensureSameThread() call, you'll get an unexpected (and fluky) error. 2.Also coroutines better to use mostly for IO operations. If your thread doing an heavyweight computations you may get a performance lack because of internal Kotlin coroutines implementation. All that coroutine marketing reports about 10_000 "lightweight threads" hides a small detail: your operations must keep a host thread in WAITING state for most a most time. 3. Coroutines aren't friendly to synchronized methods and to low level synchronization mechanisms. Everything above can be solved. But don't expect you will just add suspend keyword and everything will start to work from the box like it shown in marketing examples (except some trivial cases that are shown when Google/JetBrains trying to sell you coroutines)

please update Android oppo 8.1.0 android 9 pie we all user's request you please provide Android 9 pie

I expected something more deep and advanced , I mean beyond the basics

حد بيتكلم عربي هنا

hello dear can you guide me how to make app from website with customer layout?