We really appreciate your feedback and support, Rohan! Glad you enjoyed this 😀 Don't forget to check out the links in the description for more tips and tutorials!
Thank you so much for your feedback and support, Ehsan! Be sure to subscribe to stay updated with all the latest from Android Developers: goo.gle/AndroidDevs
We really appreciate the positive feedback, Yasser! Thanks for watching 😎 Don't forget to check out the links in the description for more tips and tutorials!
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 😁.
Thanks for taking the time to share your feedback with us, Yair! We appreciate you 👍 Don't forget to check out the links below the description for more tips and tutorials!
Thank you for your feedback, we really appreciate it 😀 We're glad you enjoyed the video! Be sure to check out the links in the description for more tips and tutorials!
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.
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.
Very informative content, thanks a lot! What if instead of passing lambda, we'll pass State and read the value as state.value? I think it should work in similar way as passing lambda. Please, let me know any insight
Hi Yerlan, thanks for watching! While this does work, we discourage it as it generally makes your code harder to write and understand. For instance, you wouldn't be able to use the "by" property delegate for state anymore and would have to change all your states read to state.value. Hope this helps clarify 🙂
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?
modern app development is already as simple as 1+1. the more you facilitate - the more you loose in performance. the rule that won't be broken for the next decade for sure.
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...
We really appreciate your feedback and support, Rohan! Glad you enjoyed this 😀
Don't forget to check out the links in the description for more tips and tutorials!
🇦🇺🪃
This video was dropped at the perfect time! thank you!
That was really informative. So many good ideas. Like how to use the layout inspector and fixing unnecessary recompositions.
Thank you so much for your feedback and support, Ehsan! Be sure to subscribe to stay updated with all the latest from Android Developers: goo.gle/AndroidDevs
We need more of this
We really appreciate the positive feedback, Yasser! Thanks for watching 😎
Don't forget to check out the links in the description for more tips and tutorials!
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 😁.
Thanks for taking the time to share your feedback with us, Yair! We appreciate you 👍
Don't forget to check out the links below the description for more tips and tutorials!
Exactly what I needed 🎉thanks a lot.
Nice! Thank you. You should also include information about your Android Studio setup since the fonts and colors look good!
Thank you for your feedback, we really appreciate it 😀
We're glad you enjoyed the video! Be sure to check out the links in the description for more tips and tutorials!
It's just the built in template, Darcula
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.
Super interesting, thanks!
Very Nice learning video
We really appreciate the positive feedback! Thanks for watching 😃
Thank you for the tip! can we have more of this please.
Love Compose, thx
We're delighted that you enjoy using Jetpack Compose, Ashwin! Thanks for the support 🙌
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.
Good stuff.
Very informative content, thanks a lot! What if instead of passing lambda, we'll pass State and read the value as state.value? I think it should work in similar way as passing lambda. Please, let me know any insight
Hi Yerlan, thanks for watching!
While this does work, we discourage it as it generally makes your code harder to write and understand. For instance, you wouldn't be able to use the "by" property delegate for state anymore and would have to change all your states read to state.value.
Hope this helps clarify 🙂
Great stuff
Thanks.
What version of android studio has this feature please?
Electric Eel which is the current canary build
Recomposition counts are in Dolphin 🐬. Recomposition highlighting is in Electric Eel ⚡
i love this
Amazing
Thanks for watching😀
If you enjoyed this video, check out the links in the description for more tips and tutorials!
👋🏼🇨🇴🧔🏻👍🏼🤝🏻 Saludos desde la ciudad de Bogotá
Next, do this work at the compiler layer so we don't have to?
My app is crashing everytime I try to use the layout inspector
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?
Thanks
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
Is it possible for the compose to defer read itself?
Thank you
It is too tricky for developing this UI
JETPACK COMPOSE : DEBUGGING RECOMPOSITION
Pleeeeeaaaaaaase fix the layout inspector. It keeps on crashing
its true
Hey Android team, I want to know that when will you launch design to code plugin for Android studio
modern app development is already as simple as 1+1. the more you facilitate - the more you loose in performance. the rule that won't be broken for the next decade for sure.
Hello don't hidden usb debbugging
Putting in setting
Add Thermal Monitor
Add Built in Gcam any Device
The recomposition is gone, but my app still has scrolling lag issue. Both Modifier.offset { } or Modifier.graphicsLayer { }. Any ideas?