I’m experiencing a lagging issue when using Paging...

# compose

[ColdDev20]

I’m experiencing a lagging issue when using Paging3 with LazyColumn while scrolling. I’ve tried refactoring to reduce nested views, but the lag persists. What’s strange is that this only happens in the version uploaded to the Play Store. When I build locally with the same variant that I used for the release, there’s no lagging. What could I do to resolve this?

[Stylianos Gakis]

Any chance you're not uploading the minified release build to play store by accident?

[ColdDev20]

It’s unlikely because I’m using the same build variant locally as on the CI that deploys to the store. But from your suggestion, do you think there might be some difference in the process between the local build and the deployment to the store? I’ll double-check to be sure.

[Stylianos Gakis]

If you're using the same minified, non debuggable build then I don't think there should be any more differences.
And is this using the same hardware and everything?

[ColdDev20]

Yes, I’m using the same device.

[Sergey Y.]

If you’re confident everything else is identical between your local build and the Play Store build, consider whether the content differs. For example, your list might include a different set of icons or images, or it could be fetching data from different endpoints (e.g., staging locally vs. production on the Play Store). Resource differences, such as large images, might also be causing lag during scrolling.

[Sergey Y.]

It’s hard to say without more specific examples. If possible, dump the APK from the Play Store and compare it to your local build.

[ColdDev20]

Which parts should I focus on comparing? Are you suggesting reverse engineering?

[Sergey Y.]

At first I would check resources