Jetpack Compose: Debugging recomposition

Показать описание

A look into how debugging a performance issue in Jetsnack and how we fixed it in Jetpack Compose. Why does deferring state reads into a lambda mean composition can be skipped?

Chapters:
0:00 - Introduction
0:37 - Three Phases Of Compose
1:40 - Deferring reads in lambdas
3:00 - Implementing the fix

Resources:

#Featured #JetpackCompose #AndroidDev

Рекомендации по теме

Комментарии

Crickey Mite!! It was actually the kind of video that many of us needed. It's like you took the video right out of our brains...

rohanmanchanda

This video was dropped at the perfect time! thank you!

KofiAccra

That was really informative. So many good ideas. Like how to use the layout inspector and fixing unnecessary recompositions.

ehsanshadi

Nicely done and in line with many recent help docs and videos from Google. So, nice though as Compose is - I can't help but feel a bit scared that you need to tread this carefully to realize rather basic UI design. Google will have to keep on praying these details because people will make those kinds of mistakes over and over again. I hope tooling will continue to improve to help catch some of this.

IncompleteTheory

Thank you for the tip! can we have more of this please.

KingFuYouTube

Since Box is an inline function and as such it does not act as a recomposition scope, shouldn't the entire SnackDetail recompose at the beginning of the video, too?

ellasaro

What valuable information 🔥. Thank you very much for this video 🙏. Now I want to debug my application, and we'll see how many recomposition defects I find 😁.

YairCarreno

Very informative content, thanks a lot! What if instead of passing lambda, we'll pass State<T> and read the value as state.value? I think it should work in similar way as passing lambda. Please, let me know any insight

yerlansarsenov

Nice! Thank you. You should also include information about your Android Studio setup since the fonts and colors look good!

gregdomski

My app is crashing everytime I try to use the layout inspector

In the Blog post, after switching to scrollProvider but still using graphicLayer's "regular" version (the steps are done in a different order), it says: "This will defer the reading of state and at least limit the scope of recomposition to just the Title composable." - But this was always the case wasn't it? Only Title compose was being recomposed right from the beginning, or am I missing something? Thanks for this video + article.

ellasaro

Is it possible for the compose to defer read itself?

LightDante

Next, do this work at the compiler layer so we don't have to?

NealSanche

Thanks, That was very helpful.
But my app keeps crashing when I open the layout inspector in both AS Dolphine 2021.3.1 and flamingo 2022.2.1 Canary 1

ngomdecadetkamdaou