Hi guys what do you have to say about this tweet a...

# compose

[Sunil Kumar]

Hi guys what do you have to say about this tweet about jetpack compose?
Just go, read that thread and put your views there and finally here as well.
https://twitter.com/Zhuinden/status/1666546308855877638?t=djIXx4sVOrlw18vDh4Dhow&s=19

[Chrimaeon]

😉
https://twitter.com/PreusslerBerlin/status/1666759823222775808?s=20

[Landry Norris]

At my last job, we converted a custom video player to full compose. Performance was actually better than on the old view system by a fair amount. Even more so when I actually bothered to check recompositions.

[Zun]

Views have 0 flaws and before compose android was perfect (sarcasm). Take his views with a grain of salt and benchmark your own app instead of relying on someone else’s opinion.

[Casey Brooks]

I’ve given precisely zero thought about performance when I use Compose, and I’ve always found it to perform way better than I would expect, even when doing something that I expected would be laggy. The only times I’ve ever noticed any issues were bugs with my own code (not remember-ing an image or expensive value, for example). I haven’t even bothered with @Stable, @Immutable or things like that, because it generally just works so well for my use-cases that I’ve never felt like I needed to bother with it.

As other’s have said, the performance is fine, there are a lot of smart folks working on Compose to make it great. It’s possible there are some significant issues, but it’s more likely that the problem is somewhere in your own code. So don’t worry about what others are complaining about, try it out for yourself and see if it meets your needs.

[eygraber]

There are a few members of the Android community that you have to learn to ignore 😬

99% of the time they complain about something, I look at my large project with 100s of modules that is fully Kotlin and Compose, builds quickly, and doesn't have any performance issues, and I just say ¯\_(ツ)_/¯

[Landry Norris]

Also, if anyone does find a scenario when it's laggy, it would be good to make sure Google's aware of it via the bug tracker. Every system's going to have bugs and issues and the best we can do as a community is to make sure Google is aware so they can fix them.

[Joseph Hawkes-Cates]

Yeah, agreed with making Google aware. I’ve found the compose dev team and the community here to be extremely responsive and helpful since I started working on this stuff in 2021. It’s helped me a lot.

[agrosner]

The guy constantly posts for attention. His arguments don’t have much backing evidence .
Our Wayfair app homepage is one of the first screens users see and let me tell you it’s faster in compose than traditional views. I think it boils down to how you optimize and expect performance. Also “slow”, is this based on release or debug builds?

[romainguy]

Compose is still a relatively new UI toolkit and the team is hard at work catching up with Views in terms of features and, sometimes, performance. There are areas where Compose is faster than Views and, unfortunately, sometimes it’s the opposite. Your feedback in that area is immensely valuable and the more data we get from real world apps, the better we can make Compose.

[romainguy]

Performance is one of our top priorities (actually the top priority) and every major version of Compose comes out with performance improvements in various areas (1.5 has several optimizations you might be interested in).

[romainguy]

Our goal since day 1 with Compose was to make you not only more productive but to let create better apps, with more interesting/beautiful UIs, exciting interactions, etc. If anything gets in your way, please let us know.

[romainguy]

Of course, we can’t fix everything right away, as much as we’d love to, so I’d like to take this quick opportunity to thank you all for your patience. We know it can be frustrating to wait for bug fixes and features to land. Just know that we’re even more frustrated than you are 😄

[andrew]

I'm just glad that we have something like compose that isn't tied to each platform release, cough cough swiftui, cough cough

[andrew]

Fast iteration helps immensely here, there's been times where I'll file a bug and it's fixed within the next release or so, and I'm unblocked.

[andrew]

I know y'all can't get to everything right away, but I know the majority of us will give you grace and kudos for all the work the teams at Google and JetBrains does for the project

[romainguy]

We’re here to help you, so keep the requests and feedback and concerns and fears and disagreements coming 🙂

[Sunil Kumar]

Agree with all of you, thanx. I myself also loving using it. We all as a team should make any issues that we face google and JetBrains aware by reporting them, that will help google and JetBrains to make it better.

I tried now in android app, with demoRelease build as well, but still while doing scrolling, it stucks little bit on images on home page. I was curious knowing more about that.

Btw, @romainguy, What major optimisations we are getting in 1.5.0, Can we read that anywhere? And by when 1.5.0 will become stable?

[andylamax]

i have learned to ignore Gabor Varadi. Upto my last point of following him (pre compose time), he always made negative comments about kotlin despite kotlin having more advantages than disadvantages.

In a way, I learn to listen to someone who offers constructive criticism rather than destructive criticism. Someone who can identify the good and the bad, is always better at being analytical than someone who always sees the bad in something despite how good it can be

[andrew]

There's a fine line between being opinionated and being a dick with tech stacks