A Clear Example of When Not to Follow Google's Best Practices for Coroutines
summary
A concrete case from T-Bank showing how following Google’s coroutines best practices can cause real problems: the talk explains why those issues arise, demonstrates other responsibilities of the main dispatcher, and presents ways to avoid the observed failures.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:28Why not follow Google
- 6:29ViewModel Scope problem
- 9:18Dispatcher switch testing
- 14:45System logs analysis
- 23:11Main thread overload
- 26:30Dispatcher choice
- 36:06Dispatcher test results
- 38:17Summary and recommendations
- 40:27Q&A
related talks
28mMy coroutines patterns and habits, 3 years later
15m5 Common Traps You Can Step Into When Using Coroutines
45mCoroutines, Flow & Android- The Good Parts
38mAndroid Coroutines: How to manage async tasks in Kotlin
40mDeep diving into the Kotlin Coroutines API
39mCoroutines vs. Threads: The True Cost of a Context Switch
45mCoroutines + Testing = ❤️ 
43mAsynchronous programming using Coroutines