Maybe. It can still have positive effect if you invoke the lambda only in some small component on screen and thus only small part of the screen recomposes.
I need an even more in depth tutorial for trying to find bottlenecks in an AndroidTV application which tend to run on slower/lower end Android devices. We have enough information how to capture logs, not how to interpret it. This video is the first which goes a bit more into depth, but I need a more general view, not just Compose
I still didn't get how the recomposition is getting skipped by passing lambdas 🤔? Also, I'd like to mention that this video has too much info to handle, I hope next time you guys split it with enough examples 😄
Those are not normal functions. They are composable functions. Internally they made these functions smart to recompose only those views whose state are changed...
My feeling is that if Jetpack Compose had been first, and now the view-based approach was released then the view-based approach would be considered a huge progress. Even now, after two years of JC release, if you make apps using JC, then the apps will have UI performance issues..
Not necessarily. We're not seeing any performance issues in our app, even in the less performant debug mode. The point of the video is that if you do have issues, you know the steps to take to resolve them
@@FahadAyaz This is the industry approach. The world started with View-based approach and discovered declarative approach (React, Vue, Swift UI, Jetpack Compose, etc.) to be much better.
Subscribe to Android Developers → goo.gle/AndroidDevs
صوري شخصي
صوري شخصية مهمة الصورة لرؤيتها بحجمها الأصلي الذي كان
3:40 3:42 3:43
Thank you so much for the video! I always admire your company's products
Outstanding comprehensive summary, but, my word, how many tools and dependencies to learn and use!?
Loved it. Cant get it any better
Amazing amazing! TY for all the tips! :)
Thank you for watching! We’re glad you found the video helpful.
Better than i phone and so called other OS❤❤❤
Thank You for sharing 🙏
Love From INDIA Kolkata 🙏
Really awesome video! Thank you so much!
Thank you! We appreciate the feedback.
Amazing 👌👌👌
how to trace the rendering part of a composable method ?
Regarding the defer reads: does it make sense to use lambdas if we are not using those deferred modifier alternatives or a custom layout?
Maybe. It can still have positive effect if you invoke the lambda only in some small component on screen and thus only small part of the screen recomposes.
@@mlykotomOh I see, so the lambdas are a way to solve the problem of unnecessary recompositions when hoisting the state?
Yes, exactly! :)
How to know when transition is finished with produceState? I'm talking about "Split heavy grames part".
Ok, looks like he is not talking about animation transition
I need an even more in depth tutorial for trying to find bottlenecks in an AndroidTV application which tend to run on slower/lower end Android devices. We have enough information how to capture logs, not how to interpret it. This video is the first which goes a bit more into depth, but I need a more general view, not just Compose
What in depth tutorial are you trying to find on an Android TV?
I still didn't get how the recomposition is getting skipped by passing lambdas 🤔?
Also, I'd like to mention that this video has too much info to handle, I hope next time you guys split it with enough examples 😄
Those are not normal functions. They are composable functions.
Internally they made these functions smart to recompose only those views whose state are changed...
where is the recomposition state in debugger. it does not exist
It's part of the regular debugger in Android Studio Hedgehog an newer.
thank u @@mlykotom
My feeling is that if Jetpack Compose had been first, and now the view-based approach was released then the view-based approach would be considered a huge progress.
Even now, after two years of JC release, if you make apps using JC, then the apps will have UI performance issues..
Not necessarily. We're not seeing any performance issues in our app, even in the less performant debug mode. The point of the video is that if you do have issues, you know the steps to take to resolve them
@@FahadAyaz This is the industry approach. The world started with View-based approach and discovered declarative approach (React, Vue, Swift UI, Jetpack Compose, etc.) to be much better.
How many performance issues give more attention to resolve?
It's not easy for an existing app to use baseline profile. Gradle related setup is really frustrating.
What do you find that's not easy for an existing app to use baseline profile?
🔥
Not so easy to understand for beginners
👍🏻
Great…
👍
👋🏻🇨🇴🧔🏻👍🏻🤝🏻 Saludos desde Colombia,🕯️🕯️🕯️ feliz día de las velitas