Are multiple nested LazyRows inside a LazyColumn s...
# compose
a
Are multiple nested LazyRows inside a LazyColumn still a no-go today in compose? I reproduced this performance issue reported here : https://stackoverflow.com/questions/75835053/android-compose-lazyrow-inside-lazycolumn-gives-junk-behaviour Are there any perf optimizations other than the @immutable? Or other tricks? Or should we avoid these kind of nesting as much as possible?
j
I haven’t personally tested on multiple device types but I do have a production app on the store whose home screen consists of a LazyColumn with three nested LazyRows. I’ve not noticed any performance issue and I’ve not seen any complaints.
👍 1
👍🏽 1
a
Test case is launching 100 items, I imagine that staying with only a few nested rows should be ok
m
same issue, specifically on Android TV devices, which is almost low spec comparing to mobile. But using kotlin/xml using recyclerview fixes this issue
c
apparently compose 1.9 has little to no lag so id make sure to test with that. FWIW. Ive used lazy rows and horizontal pagers in lazy columns for a while without any real issues.