Enhancing Jetpack Compose app performance

Рет қаралды 31,006

Android Developers

Күн бұрын

Пікірлер: 41

@AndroidDevelopers 11 ай бұрын

Subscribe to Android Developers → goo.gle/AndroidDevs

@GsuegGeheh 8 ай бұрын

صوري شخصي

@GsuegGeheh 8 ай бұрын

صوري شخصية مهمة الصورة لرؤيتها بحجمها الأصلي الذي كان ‏‪3:40‬‏ ‏‪3:42‬‏ ‏‪3:43‬‏

@DanielJohnGay 8 ай бұрын

Thank you so much for the video! I always admire your company's products

@mark-147 11 ай бұрын

Outstanding comprehensive summary, but, my word, how many tools and dependencies to learn and use!?

@hellosagar 10 ай бұрын

Loved it. Cant get it any better

@AlejandraStamato 11 ай бұрын

Amazing amazing! TY for all the tips! :)

@AndroidDevelopers 11 ай бұрын

Thank you for watching! We’re glad you found the video helpful.

@ScanaRch 11 ай бұрын

Really awesome video! Thank you so much!

@AndroidDevelopers 11 ай бұрын

Thank you! We appreciate the feedback.

@VIDEOSANDREEL 11 ай бұрын

Better than i phone and so called other OS❤❤❤ Thank You for sharing 🙏 Love From INDIA Kolkata 🙏

@TimRijckaert 8 ай бұрын

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

@cameronbateau6510 6 ай бұрын

What in depth tutorial are you trying to find on an Android TV?

@coldwised 8 ай бұрын

How to know when transition is finished with produceState? I'm talking about "Split heavy grames part".

@coldwised 8 ай бұрын

Ok, looks like he is not talking about animation transition

@Programmer-b9q 11 ай бұрын

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..

@FahadAyaz 11 ай бұрын

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

@mr-turkish 11 ай бұрын

@@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.

@cameronbateau6510 6 ай бұрын

How many performance issues give more attention to resolve?

@hasa4628 10 ай бұрын

how to trace the rendering part of a composable method ?

@yasserakbbach708 11 ай бұрын

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 😄

@deepakbisht4957 11 ай бұрын

Those are not normal functions. They are composable functions. Internally they made these functions smart to recompose only those views whose state are changed...

@PedroBarbosaRoman 10 ай бұрын

Regarding the defer reads: does it make sense to use lambdas if we are not using those deferred modifier alternatives or a custom layout?

@mlykotom 9 ай бұрын

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.

@PedroBarbosaRoman 9 ай бұрын

@@mlykotomOh I see, so the lambdas are a way to solve the problem of unnecessary recompositions when hoisting the state?

@mlykotom 9 ай бұрын

Yes, exactly! :)