12:00 You can use DI libraries like Dagger, Dagger Hilt, Koin and inject application context in your viewmodel, use case, repository, data source layers.
The guy who asked about what is there any plans for making compose smart enough to avoid ending up with poor UI performance I would like to say THANK YOU. To all panelists, this is why there is someone asked about why the Android development experience is becoming hard and harder, when you innovate a new feature to compete with the market needs & trends that are now driven by the frameworks that respect the Declarative UI like Flutter or Swift UI in iOS, please make sure you are putting into your consideration such kind of complexities you are adding when working in shipping such features, I don't have to spend much time or even fight your new feature e.g. "Jetpack Compose" to come up with a performant UI, basically this shouldn't have to be the developer problem, providing tools like the one you mentioned here such as "Compose tracing" even to spend more time looking into these traces and figuring out what's going on, developers should have to be more focused into implementing the business requirements not figuring out how to optimize your offering to fit their needs. Of course, I appreciate every single contribution you have made so far and you're doing a fantastic job, however this really needs to be settled.
![[LIVE] : ONE ลุมพินี 88 | คู่เอก "ป้อมเพชร vs อัสลามจอน"](http://i.ytimg.com/vi/1ZqTVVbMgbo/mqdefault.jpg)
12:00
You can use DI libraries like Dagger,
Dagger Hilt, Koin
and inject application context in your viewmodel, use case, repository, data source layers.
The guy who asked about what is there any plans for making compose smart enough to avoid ending up with poor UI performance I would like to say THANK YOU.
To all panelists, this is why there is someone asked about why the Android development experience is becoming hard and harder, when you innovate a new feature to compete with the market needs & trends that are now driven by the frameworks that respect the Declarative UI like Flutter or Swift UI in iOS, please make sure you are putting into your consideration such kind of complexities you are adding when working in shipping such features, I don't have to spend much time or even fight your new feature e.g. "Jetpack Compose" to come up with a performant UI, basically this shouldn't have to be the developer problem, providing tools like the one you mentioned here such as "Compose tracing" even to spend more time looking into these traces and figuring out what's going on, developers should have to be more focused into implementing the business requirements not figuring out how to optimize your offering to fit their needs.
Of course, I appreciate every single contribution you have made so far and you're doing a fantastic job, however this really needs to be settled.
this was a very good session! The questions after the live stream got a little crazy ...
so nice Live stream from Google Andrid team! Thanks!
Where is Chet Haase?
he slept in
Thanks
Ok thanks
Esse vídeo é sobre o q ?
111th...Thanks
Beta tester od roku 2016 oceňujem,,