I have 32 view types in recycler view. I think its...
# android-architectureu
ursus
05/11/2019, 6:08 AMI have 32 view types in recycler view. I think its too much. But most of them are variations of the same (like item A with and without header, or item A with big margin left to visualize nesting).
Maybe it makes sense to have that be the same view type and visible/gone the header in on bindview?
Is there some perf penalty to this? In my head it causes layout, but so does setting text on wrap_content height textview.
What would be the heuristic to create a new viewtype if views are like that? (variations of the same?)
m
Miguel
05/11/2019, 6:42 PMSometimes is better to sacrifice some performance for the sake of maintenance ¯\_(ツ)_/¯
t
tschuchort
05/12/2019, 1:24 PMPerformance would be better because then the recycling works more effectively. Facebook had the same problem and created the litho library, which works basically the same as react vdom
u
ursus
05/12/2019, 2:05 PM@tschuchort Better performance with having the header everywhere and gone-ing it?
t
tschuchort
05/12/2019, 2:07 PMI think so. The recycler view can only recycle when the view type is the exact same, even when they are actually almost identical. Just imagine a RV where every view had a different type. There would be 0 recycling
tschuchort
05/12/2019, 2:07 PMYou can read more about that in the posts about litho
u
ursus
05/12/2019, 2:07 PMyes but I dont think its what they did in litho
ursus
05/12/2019, 2:08 PMafaik they break apart the view with havingg separate viewtype for header only and then viewtype for body
ursus
05/12/2019, 2:08 PMso its unrelated views that only look related
ursus
05/12/2019, 2:09 PManyways, im with you on the perf (I think its correct), but then you consume more memory having views in evry row you dont ever show)
4 Views