4 Ways To Debug Recomposition in Your Jetpack Compose UI!

Рет қаралды 943

Күн бұрын

💻 Join my new Refactoring Legacy Code course now: bit.ly/47dzTLT
In this video, I will demonstrate four ways to handle recomposition within Jetpack Compose UIs. First, I will show you how to detect recompositions, followed by identifying their sources.
🔗 Links:
- Stack Overflow - stackoverflow.com/questions/6...
- rebugger repository - github.com/theapache64/rebugger
=========================
📩 Checkout My 👇
bit.ly/YCNewsletter102
=========================
📩 Sign up for my new newsletter 👇
bit.ly/YCNewsletter102
=========================
Join my Community on Discord 👇
/ discord
👨🏽‍🏭 Who I am:
I'm Younes Charfaoui, a Software Engineer and an Android Developer. I make videos about Android development, Technology, and productivity for software engineers.
😋 Be My Friend:
💻 GitHub - github.com/Younes-Charfaoui/
🐦 Twitter - / charfaouiyounes
📑 Medium - / mxcsyounes
📷 Instagram - / charfaoui.younes
🌍 My website - www.charfaouiyounes.com

Пікірлер: 8

@abhishektripathi6957 Ай бұрын

very helpful content

@user-ml6qs4zk8z 25 күн бұрын

thank you it's very helpful

@iamkadircan 2 ай бұрын

thanks for this great content

@DiabloZq 3 ай бұрын

Thank you!

@georgikopchev1739 3 ай бұрын

good stuff (y)

@ChrisAthanas 3 ай бұрын

Nice work

@moaliyou 2 ай бұрын

So is it necessary to solve every recomposition? For example in this case the text can't be dependent on the function

@Alchemist10241 2 ай бұрын

No you don't need to solve every recomposition. you should do this only after you build the release built using R8 and still having performance issues related to recomposition.