at the moment the main thing it gives you is “virtualization”, in that it will only render the rows needed to fill the screen. it does not “recycle” the rows in the same way that recyclerview would or does. This is less important for compose, however there are still some things somewhat similar to recycling that we could try that would be very easy to achieve with this implementation but have not yet
02/13/2020, 3:33 PM
basically Baby Step 🙂
Leland Richardson [G]
02/13/2020, 3:39 PM
the API isn’t stable or finished yet, but i’m not sure I’d call it a baby step either. We expect virtualization to be pretty much “all we need”.
02/13/2020, 8:00 PM
the hope is, as Leland said, that Compose layouts are much lighter-weight than Android `View`s, and thus that recycling will be unnecessary
02/13/2020, 9:10 PM
Very interesting and original solution, but we will have to see with 'heavy' layouts how it behaves.
Something tells me that this API will be stable for next I/O 🙂