Manuel Vivo

Collecting in a lifecycle-aware manner is essential for saving system resources. Since coroutines and flows are the recommended solution for asynchronous programming on Android, there are APIs that do most of the heavy-lifting work for you. Namely: repeatOnLifecycle, flowWithLifecycle, and Compose’s collectAsStateWithLifecycle. When building for Android, you should include these libraries in your toolbox. But even if you’re doing KMP, you should keep this in mind. In this talk, we’ll see the different lifecycle-aware coroutines APIs, the problems they solve, and which types of flows can make your system waste resources—Disclaimer! A cold flow backed by a Channel or Flow operators with buffers might be under investigation. Prepare to roll up your sleeves as we dissect their implementation details and learn low-level coroutines and Compose APIs. But the journey doesn't end there! To help you think as a library developer, we’ll explore an API regret that never made it into stable to protect developers from misusing the API and force them respect coroutines’ structure concurrency. By the end of the talk, you'll understand the importance of collecting in a lifecycle-aware manner, use low-level coroutines APIs to build your own APIs, and design APIs that respect structure concurrency and protect your users from misuse.

In this community-driven keynote, you'll hear from Android experts as they deliver their hot-takes, predictions, and advice about how they see Android evolving and how you can best prepare for that future. Join us as they answer the question: Where do you see Android Development in three years, and how do you think developers should prepare for that future? After all experts are done making their pitch for the future...its your turn to ask the questions in a rapid-fire Q&A format.