Wonderful. Thanks Sir. I wonder how much it differs in terms of performance in comparison to the nested version. Yes, if the UI gets more complex it would be more noticeable, but what is the gain with a LazyColumn which has as its items these cards (nested version vs constraint version). Is the performance difference noticeable? In the future when I am more confident with jetpack I will check the ui performance for myself, but it would be nice if you could give some estimates.
The official take from the Google is - the performance difference between XML and Composable is negligible with XML getting slight edge in complex UI rendering. However they also claim that the trade off in terms of ease of development with Composable with all UI code being in one place, is worth it. Over last many years now, with reactive paradigm Composable attempts to do the same thing.
Thank you. Well explained.
You are welcome!
Wonderful. Thanks Sir. I wonder how much it differs in terms of performance in comparison to the nested version. Yes, if the UI gets more complex it would be more noticeable, but what is the gain with a LazyColumn which has as its items these cards (nested version vs constraint version). Is the performance difference noticeable? In the future when I am more confident with jetpack I will check the ui performance for myself, but it would be nice if you could give some estimates.
The official take from the Google is - the performance difference between XML and Composable is negligible with XML getting slight edge in complex UI rendering. However they also claim that the trade off in terms of ease of development with Composable with all UI code being in one place, is worth it. Over last many years now, with reactive paradigm Composable attempts to do the same thing.