Does anyone talk about the performance of Jetpack Compose? I have tried various samples e.g JetNews and the scrolling, behavior and transitions of different elements does not match native elements like RecyclerView. Is this expected because compose is not fully native?

JetNews is not implementing

RecyclerView

. it uses

ScrollableColumn

which is not equivalent of the

RecyclerView

@Jeff I feel exactly the same, Performance of LazyColumn is not even close to a native view like RecyclerView, I create an issue, please star it, or maybe you can create another issue https://issuetracker.google.com/issues/176523912

There is nothing non native in compose, it's just matter of current implementation performance

@Marko Novakovic we are on the same page on that.

something worth mentioning of what’s missing from

LazyColumn

is prefetching, i.e. the ability to fetch+preload images before views are actually rendered. obviously not the entire scope of performance problems though, hopefully things get much better soon

I am unable to look into the source code of Jetnews at the moment, but the sluggish

lazy column

isn’t due to the

imageResource()

function correct? Last time I checked, it was loading images synchronously and causing a noticeable lag.

Known issue in some of the touch handling for showing ripples. cc @matvei

Ripple showing while scrolling could be one of the reasons for frames skip in LazyColum.

Ripples should be delayed a little bit in the scroll containers, that's what happening in views and recycler view. It's not the case for compose, but we're looking into it, thanks

@matvei I'm still facing this issue in Beta 2, is there any way to disable it ?

Not fixed yet, still on our radars. I don't think you can disable it anyhow other than implementing your own ripples and delaying them, but even that would be a workaround

How about the poor scrolling. The scrolling of items and calendar days in the Crane sample app is very poor. It's like frames are dropping. Not a match to RecyclerView