More performance tips for Jetpack Compose

i know this is almost a year old, but could you please add timestamps? this is quite a lot to digest so we need it to go back and fort to rewatch specific topics.. thanks

is interfaces are stable?

does anyone know where to find <module>-composables.txt file?

dear god. I need to cry a bit

TopAppBar scrollBehavior still janking so much . Like exitUntilCollapsed Behavior() - > with nested connection to lazyColumn . So much janking fix it

I had a doubt that will if i have two composable nesting from a parent composable, and there is a mutable list passed to the first child but no change occurs to second child but it still recomposes. But if the parent is itself part of a list than will all the instances also recompose runtime or only the particular list item affected ?

am I the only one who thinks that all of this is very difficult to remember? I have more than 5 years working with Android and everyday there's something new to improve

amazing, understanding compose day by day

Thank you for this video! Performance tips are always helpful. 🙏🏻

Awesome!

great presentation. I like "tools over rules" approach and frequent disclaimers

How Google devs sleep 😴 after creating another "best practice more performance industry standard" code to remember every 6 months.

Beta tester od roku 2016 oceňujem,,

That's a lot to remember and check. Please move as many checks into Android Studio warnings as possible!

Very informative 👍

and the perfect title can be honeymoon is over let's face with realities

day by day, they are discovering how compose is complex and it is not easy to maintain 😂😂
thanks, but i will continue to work with activities and fragment happily 🎉

That's lot to remember

Very thanks

Then why even have non-lambda modifiers, if they are most of the time less performant??