Very usefull video. Coming back here to watch some tricks again and again, so I decided to write some timecodes to help myself and maybe some of you too: 1:00 - Configuration 1:55 - Something to remember 3:57 - LazyList Key 5:47 - derivedStateOf 8:10 - Compose primary phases 9:57 - defer reading state 11:36 - Running backwards (Backwards write) 15:26 - Covering your bases (Baseline profiles)
We're delighted that the tutorial was helpful to you, Ken! You can check out the Android Basics with Compose course here for even more Jetpack Compose fun: goo.gle/3V7Vlgg
I recommend looking at "composable metrics". Chris Banes has a blog post on it. It will generate a report on all your composable functions. Composable metrics tells you if a composable function is restartable and skippable. And if Compose can infer if an object is stable or immutable.
We're delighted to hear that you've enjoyed the tutorial. If you'd like to learn more about Jetpack Compose, please check out this resource: goo.gle/compose-pathway 🤩
Happy to hear the tutorial was helpful, Stefan! If you’re interested in additional resources, check out the Jetpack Compose walkthrough here: goo.gle/3p7WO7l
Indeed it is! You can find the additional resources for this lesson here: JetPack Compose Performance → bit.ly/3xNSSwI Baseline Profiles → bit.ly/3tUmF5G Jetpack Compose Phases → bit.ly/39HNK5k
4:14 if item 5 and 4 are swapped, then only they should be recomposed, right? Items 1, 2,3, 6, 7 and subsequent items will keep their indexes which are used as keys. Do we need a LazyList Key in this case?
So the macrobenchmark library let's us see what the improvements might be for the user in the release build but does not guarantee it? And also we do not need to do anything to ensure baseline profiles are added to the app, it's added by default. Is that right?
Depends on what you want it to change. If you are adding or removing sub-composables, or changing the size or layout then recomposition or layout will be triggered. In the case of the example only the color changed, everything else remained the same, so it only affected how the background was drawn (the function of drawBehind). Other functions, e.g. drawWithCache or drawWithContent, may be better suited to what you need. A good question to ask may be why the value frequently changes. E.g. a clock implementation may only need to redraw some aspects (text/hands) and the rest (ticks/frame/etc.) may be subject to caching.
Very usefull video. Coming back here to watch some tricks again and again, so I decided to write some timecodes to help myself and maybe some of you too:
1:00 - Configuration
1:55 - Something to remember
3:57 - LazyList Key
5:47 - derivedStateOf
8:10 - Compose primary phases
9:57 - defer reading state
11:36 - Running backwards (Backwards write)
15:26 - Covering your bases (Baseline profiles)
Wow very nice video and love the comedy parts and the narration. So natural. Please keep making more videos like this.
Legends say that even to this day, Chuck is still waving to you.
On a more serious note, great content, it was very helpful!
We're delighted that the tutorial was helpful to you, Ken! You can check out the Android Basics with Compose course here for even more Jetpack Compose fun: goo.gle/3V7Vlgg
@And 0:21 roidDevelopers
More of this! This is extremely helpful. Personally I'd like more tips on to spot and avoid unnecessary recompositions.
I recommend looking at "composable metrics". Chris Banes has a blog post on it. It will generate a report on all your composable functions. Composable metrics tells you if a composable function is restartable and skippable. And if Compose can infer if an object is stable or immutable.
@@robchr Cheers for that pointer, this looks very interesting indeed.
🎊🎊🎊😣😣😣🎊🎊😣🎊😣😣🎊😣😣😣😣😣😣😣😣😣😣😣🎊🎊😣🎊😣🎊🎊🎊😣🎊🎊🎊🎊🎊🎊🎊🎊🎊🎊🎊😢😢🎊🎊🎊🎊🎊🎊🎊🎊🎊🎊🎊🎊😢😢😢😢😢😢😢😢😢😢😢😢😢😢😢😢😢😢😢😢😢😢😢😢😢😢😢😢😢😢😢
@@robchr ⁹
@@robchr🐶🐶🐩🐩😃😃😃;-):-C-);-) bjjjjjcvbbvvvnjo🐶🐶🐶🐶🐶🐶🐶🐶🐶🐶
More of this, please. Something I have learned is one learns quite a lot about a new language/platform when one programs for performance.
Thank you for the Summary at the end.
Glad it was helpful! 😁
The uggliest thing about Compose and which applies to each new stuff is when it allows you to do something which is not recommended to do.
This is really useful. Thanks!
Great content! While watching this I was litterally dealing with startup jank, that is probably now just the JIT.
We're happy to hear this video helped! 😄
Thank you for this video and to the dev team, keep going, you are on the good way !
This is a very helpful video for compose optimizations, appreciate it.
Very useful information!🙏🙏
Thank you so much for this video! Enjoyed to the max
We're delighted to hear that you've enjoyed the tutorial. If you'd like to learn more about Jetpack Compose, please check out this resource: goo.gle/compose-pathway 🤩
The most completely class about compose tricks... thank you so much :)
This is good stuff. I owe you guys some ☕
Thanks for the coffee, Jerry! Have you checked out our Jetpack Compose walkthrough? You can learn more here: goo.gle/3MK5Xhy ☕
Cool content !!!
Amazing, short and on the point, keep up the good work
Great Presentation !!
We really appreciate your support! Thanks for watching 🙂
This helps a lot!
Happy to hear the tutorial was helpful, Stefan! If you’re interested in additional resources, check out the Jetpack Compose walkthrough here: goo.gle/3p7WO7l
We want more of this from Engineers from inside.
Is this information available in a blog post or in the compose documentation?
Indeed it is! You can find the additional resources for this lesson here:
JetPack Compose Performance → bit.ly/3xNSSwI
Baseline Profiles → bit.ly/3tUmF5G
Jetpack Compose Phases → bit.ly/39HNK5k
This was a really information dense video! But very well presented nonetheless
hi Ben and Chuck!
Nice❤ 0:53
Simply awesome
Right back at you.✨
Great
Thanks so much, Mohammad! Since you liked this video, come check out our Jetpack Compose playlist for more on this topic 😊
4:14 if item 5 and 4 are swapped, then only they should be recomposed, right? Items 1, 2,3, 6, 7 and subsequent items will keep their indexes which are used as keys. Do we need a LazyList Key in this case?
Why was this not highlighted in first place
So the macrobenchmark library let's us see what the improvements might be for the user in the release build but does not guarantee it? And also we do not need to do anything to ensure baseline profiles are added to the app, it's added by default. Is that right?
Good moreng
If I use Canvas(modifier = ..) in Compose and pass value which frequently changes, should I use drawBehind method? And how? Put Canvas in this method?
Depends on what you want it to change. If you are adding or removing sub-composables, or changing the size or layout then recomposition or layout will be triggered. In the case of the example only the color changed, everything else remained the same, so it only affected how the background was drawn (the function of drawBehind).
Other functions, e.g. drawWithCache or drawWithContent, may be better suited to what you need.
A good question to ask may be why the value frequently changes. E.g. a clock implementation may only need to redraw some aspects (text/hands) and the rest (ticks/frame/etc.) may be subject to caching.
Do you really need R8 enabled? Will Compose be slower without it than the xml view system?
Yes but you wouldn't ship your app without R8 in any case. For local development it's not such a huge deal
🙌🏻🇨🇴🧔🏻👍🏼🤝🏼 Saludos desde Colombia.
Wow
How can i to hide a top bar(scaffold)? in specific screens
it destroyed my brain !
PLZ show a beautiful solution!
Hello Dimid, please check here for more information regarding Material Components and layouts in Jetpack Compose: goo.gle/3IEPp8K
0:48
Please don't make presentation code dark them and other stuff light theme
poor Chuck
This is very useful. Thanks!
Appreciate the feedback, Abbasali! Don't forget to subscribe for more 😎👍