Collecting flows in a lifecycle-aware manner

Manuel you are doing a lot of job to improve how Android should be taught. Finally you guys from Android speak slowly, put emphasis on the words, and furnish a lot of visual tools, and explain clearly the problem you are going to solve, then repeat in a structure what you say, and finally we have an app android now that put in practice everything.

This API is just ugly, why do we have so many lambdas nested? Why not have it as clean as LiveData?

thanks

Thanks

That's why LiveData might be outdoing Flows. Integrating lifecycle into your flows this way always creates a new coroutine, for example, when the app is sent to bg (STOPPED) and brought back to fg (STARTED) again. If you had LiveData, you could just observe it w/out this overhead and latest data would always been republished when necessary.

The problem of the collect manner is too many workable ways that let junior developer may use incorrectly.

Not sure wha the point of this is given that there has already been a lifecycle api available for years and you can use it in a viewmodel where you can do your flow collection.

Thankss and byebye live data

Ok thanks