Great Video! I have been learning android+kotlin for a while now and the main challenge is most resources in the internet don't rly suit my learning style, but ur videos do!.
Thank you so much Rahul! It would be really awesome if you could give some directions about the last point "Fitting coroutines into your app architecture" or maybe a video in the future if that's possible. Thanks a bunch!
definitely! I went through the Google codelab which was pretty helpful (MVVM architecture): codelabs.developers.google.com/codelabs/kotlin-coroutines/index.html I'll keep this in mind as a video idea! There's a lot more to talk about with coroutines.
That was great content, Rahul! I would request you to do videos or point me toward resources for the extra topics you mentioned at the end of the video.
Rahul sir please make projects tutorials including advance topics like MVVM, Dagger , Dependency Injection, etc. in Kotlin. Sir fortunately we got time due to this pandemic, as we have to submit college projects. Please sir🙏
Thanks Rahul for the great content. It'd be really good if you could make a video on how to implement this with CLEAN architecture, repository pattern, flow and liveData
Have a question at timestamp 4:10 line # 67 in code shown. You mentioned "finally back on the main thread" How did you get back to main thread ? Is the onResponse Method on line # 60 executed in main thread ? I am unable to understand how you switched from background thread (where API call was made) to main thread. Or am I missing something basic here ? On line #67 i tried to put println(Thread.currentThread().id) But that didnt printed "main". So are we really back to main thread ?
Retrofit will invoke the callback method in the main thread - this is not something I did. (the actual network request + JSON parsing will happen in a background thread). What do you see when you print the name of the thread? Thread.currentThread().name
key comment, "simple and light thread" all you are doing is taking out all of the error handling function. Most of those "60" lines of code are error handling giving you information back. Now when you get an error you have nothing telling you why.
Hey Rahul, you're doing great... Yes we want more videos on the topic as you explain cleanly and concisely, Thank You 🤗🤟
Thanks Jayesh, and I've made note of your feedback 😊
I don't comment often, but this video was very informative and well structured, great work!
Thanks so much, I really appreciate that.
Yes, we want more videos on the topic as you explain cleanly and concisely, Thanks.....
💗
At first, I was like i know coroutines and I don't need to see this and then I saw it and now I know coroutines better. Thanks
Wow, that's high praise, thank you Arpit.
Great Video! I have been learning android+kotlin for a while now and the main challenge is most resources in the internet don't rly suit my learning style, but ur videos do!.
Glad to hear that 🤗
This helped me to understand coroutines even better! Thank you! God bless you!
I'm so glad! Thanks!
Thank you so much Rahul! It would be really awesome if you could give some directions about the last point "Fitting coroutines into your app architecture" or maybe a video in the future if that's possible. Thanks a bunch!
definitely! I went through the Google codelab which was pretty helpful (MVVM architecture): codelabs.developers.google.com/codelabs/kotlin-coroutines/index.html
I'll keep this in mind as a video idea! There's a lot more to talk about with coroutines.
super clear and helpful explanation as always, thank you so much!
Good work. Your videos are really very helpful & easy to understand the concept. Will definitely waiting for other videos 👍🏻
thanks Varsha!
I Was Really waiting for this video. Thanks Sir
I've also been waiting for this video 😂
very concise and clear. Please make videos on kotlin design patterns.
Thanks! I have a few more videos about Kotlin
Nice explanation with example. Great work. 👍
thanks!
Very simple and great example thx
That was great content, Rahul! I would request you to do videos or point me toward resources for the extra topics you mentioned at the end of the video.
Thanks Tanish! I've found the Kotlin docs about coroutines to be pretty good: kotlinlang.org/docs/coroutines-overview.html
Rahul sir please make projects tutorials including advance topics like MVVM, Dagger , Dependency Injection, etc. in Kotlin.
Sir fortunately we got time due to this pandemic, as we have to submit college projects.
Please sir🙏
Thanks for the feedback, let me see what would be interesting 😊
Very nice
Great video, keep them coming!
Thank you Sriram
nice work
Thanks Rahul for the great content. It'd be really good if you could make a video on how to implement this with CLEAN architecture, repository pattern, flow and liveData
+1.
thank you Melanie, I'll add it to my list
Nice, you explained it very clearly great 👍
Thanks Shivender 😍
Thanks a lot for this informative video!
thanks Mihir 😍
Thanks brother
hope it makes sense :)
Saw the first 10 mins and it does so far thanks 🙏
Great work
💝
Amazing!
Very interesting and informative.
🙏🙏
Plz make more videos step by stem to advanced topics
will do
Awesome explanation and secret of behind speaking fluent English with native tongue ?
Helps to be born in the US 😇
Cool
Error
Retrofit Annotation not found (Pram #2) ..?
Have a question at timestamp 4:10 line # 67 in code shown. You mentioned "finally back on the main thread" How did you get back to main thread ? Is the onResponse Method on line # 60 executed in main thread ? I am unable to understand how you switched from background thread (where API call was made) to main thread. Or am I missing something basic here ?
On line #67 i tried to put
println(Thread.currentThread().id)
But that didnt printed "main". So are we really back to main thread ?
Retrofit will invoke the callback method in the main thread - this is not something I did. (the actual network request + JSON parsing will happen in a background thread).
What do you see when you print the name of the thread? Thread.currentThread().name
key comment, "simple and light thread" all you are doing is taking out all of the error handling function. Most of those "60" lines of code are error handling giving you information back. Now when you get an error you have nothing telling you why.
Still waiting for that "Ex-Stanford, Ex-Pinterest" name drops in your thumbnails and titles
ahahaha I was leaving that for the few people who venture over to the "About" section 😇
it is not a beginner tutorial. kindly make a simple start. i am skipping.
sorry this didn't work for you. Can you share an example of what you consider a good beginner tutorial?