Compose performance - Android Developers Backstage

Listen to the podcast → goo.gle/44sbO32
Episode 199: This time, Romain, Tor, and Chet talk with Leland Richardson, George Mount, and Chuck Jazdzewski from the Jetpack Compose team about performance. The team has been looking at performance issues recently and discusses what they’ve found, what gotchas lie in wait for library developers, what tools and compilers can magically handle for you... and what they can’t. Tune in to learn about why we worry about autoboxing (and why you probably shouldn’t).
Catch more from ADB → goo.gle/adb-po...
Subscribe to Android Developers → goo.gle/Androi...
#Featured #AndroidDevelopers #ADBPodcast

[@AndroidDevelopers]

Listen to the podcast → goo.gle/44sbO32

[@admqueiroga]

What an episode! Incredible content guys!

[@shridharpandeyofficial]

I don't know why but .. XML feels more comfortable for me than Compose. I feel that XML gives more control over UI and Application as compared to Compose. I would like to have a conversation if anyone can join.

[@nah922]

So, when are they going to spill the beans about Compose being discontinued? 😄 But jokes aside, I must say that the idea behind Compose is pretty cool, though the execution needs some work. You know, we've seen how badly the Threads app performs, especially on those not-so-fancy devices.
I think there are two critical issues with Compose that need some TLC:
1. Performance: Even if you do everything right and follow all those official guidelines, it's a bummer to see the performance go down, especially on budget phones.
2. User-friendliness: Don't get me wrong, Compose is a game-changer, but it can be a bit tricky to get the hang of it. There are so many gotchas, and it doesn't cut much slack for developer mistakes. I mean, we've got to follow all these rules, and sometimes they make the whole declarative thing lose its charm. Sure, we can whip up a screen pretty quickly, but dealing with state and data flow feels like a tightrope walk, where a tiny misstep can cost you big time.
Let's hope they sort these things out and make Compose even more awesome! 🚀

[@freedomchuks]

this is very interesting and knowledgeable, thanks this really amazing!

[@eddyyoelfresnohernandez9442]

I was hopping to get a bit of LazyColumns performance :(

[@Daaaaaaavid]

Thanks, just moved the sorting to the VM

[@svpskio]

Interesting chat, thanks for sharing!

[@ankitsingh-rb8pc]

whenever we load a compose view inside a view holder of native recycler view there is a lag when the view comes for the first time but after that scrolling becomes smooth.
what is the reason for this and is there any way to fix it ?

[@VitusHafter]

Compose perfomance again😁

[@jcddcjjcdnz]

The problem with Compose is that it comes with so many caveats. Stick with views. Proven and reliable. Also, the Threads app version done in Compose is not great, and I believe it has been withdrawn.

[@eddyyoelfresnohernandez9442]

Is it possible to get Threads compose code? :|

[@oraofficial7899]

"stick with view" , what do you mean by "view" ?, XML layout development ?

[@vaelinalsorna1649]

I was a developer at a big bank and we were using compose with no major issues. This wasn't a small app either and there were almost 100 android devs working on the app. Everyone was happy with compose and keeping the devs happy was good enough reason to adopt it.