Is Jetpack Compose not optimized for big projects?...

# compose

[Aaron Waller]

Is Jetpack Compose not optimized for big projects?
I tried now for 1 1/2 Weeks to get my performance right but didn’t succeed.

Now I finally figured out that it has something to do with the sheer size of my project.
When I simply comment out the the call to my MainScreen() inside the setContent{} method and put in some different code (for example Horizontal Pager + Tab Layout + LazyVerticalGrid) it performs worse in my big project than in a freshly created one even though it is running the exact same code.
Only difference is that the laggy project has hundreds of other classes in it (which are not getting called cause I commentet out the call to MainScreen) and a lot more dependencies.

Running both projects in Release + R8 enabled

So as stupid as it sounds but I just simply have to give up on Jetpack Compose and get back to XML…
I’m loosing hope

[Landry Norris]

What Compose version are you using? I believe they made some improvements to performance in 1.3 due to applying modifiers.

[Aaron Waller]

1.2
Gonna give it a try now

[romainguy]

Have you run perfetto/systrace and the profilers to see what’s going on?

[Zoltan Demant]

Fwiw, I don't think project size in and of itself will negatively impact performance (at least not that much). I haven't noticed any difference when working on 10k LOC project vs 500k.