I might be stating an obvious fact, but noticed on...
# compose
k
I might be stating an obvious fact, but noticed one thing today and thought I should share the same. When you’ve many UI components (Button, Text, Progress bar, etc.) cluttered in smaller region and this region is going to get re-composed highly frequent due to some state changes, I simple
Row
Column
based Composable works way better than
ConstraintLayout
. So you might lose some alignment constraint provisions but there won’t be any performance hits.
ConstraintLayout
was accumulating lag over the time while
Row
,
Column
being simple enough, was able to handle heavy operations.
g
This is how I started doing it, it reminded me of how we'd do stuff in bootstrap or something, makes a lot of sense