I'm trying to pinpoint performance issues (laggy LazyColumn). I'm testing that on release+R8 (on Hua...

# compose

[Michal Klimczak]

I'm trying to pinpoint performance issues (laggy LazyColumn). I'm testing that on release+R8 (on Huawei P20 lite Android 9), but it's still not good. I don't really understand what kind of difference should I expect between release+R8 on development machine and google play version and wanted to try to simulate that.
Found:

adb shell cmd package compile -r bg-dexopt my.app.id

But it only shows me

Failure: package my.app.id could not be compiled

My second question is - can I somehow test the final experience, e.g. should deploying to Firebase App Distribution work as fine as Google Play or not really?

[Sergey Y.]

The obvious question is, did you pass in your actual app id instead of the hardcoded my.app.id?

[Michal Klimczak]

I did 😄

[Michal Klimczak]

I also tried assembleFlavorRelease and then adb install and then adb shell cmd package compile... but that worked exactly the same.

[Sergey Y.]

Can you test on some other device?
This could be Huawei specific.

[Michal Klimczak]

that's a good idea, will try. on huawei it's lagging, that's why I tried there first

[Will Shelor]

In my experience, the difference is about 10% of the performance. The difference is because of the JIT compilation of Compose. If you wanted to try to see if this is the source of your problems, you could launch the app, run it a bit, close it, launch it again, run it, and close it, over and over

[Will Shelor]

if this eventually causes it to work without jank, then the profiles from Google Play would help; if not, they wouldn’t help. I’d probably recommend profiling, and seeing if you can see any suspicious recomposition when scrolling. Ideally the only point that should see recomposition is when new elements come into view.

[Michal Klimczak]

that's a good hint, thanks