Is ConstraintLayout still preferred over nested Column & Row in Jetpack Compose?

user_11074576 0
Viewed 1128

Before Compose, when creating complex UI with XML, it's recommended to avoid nesting views (RelativeLayout and LinearLayout), and encouraged to use ConstraintLayout for achieving complex layouts.

Now Compose has come out, and just by looking at it, ConstraintLayout in Compose was so complicated to understand, from my perspective—it's taking more time to figure out how the view should look like with ConstraintLayout than with nested Column and Row.

Honestly, I'd rather go with nested Column and Row than ConstraintLayout in Compose, but I'm not sure about its drawbacks.

android-constraintlayout android-jetpack-compose kotlin android
2 Answers

Short answer: No, nested Rows/Columns should be fine.

Compose is designed to reduce the penalty for nesting layouts, and allow for layouts to be more easily...well, composed. The View system requires non-trivial overhead for each View you create, so it was encouraged to avoid nesting them more than necessary and creating extra Views.

While it's hard to say that there are no situations in which nesting Rows and Columns will cause a performance problem where ConstaintLayout would work well, you shouldn't immediately jump to ConstraintLayout when using nested Rows/Columns would allow you to more easily express your desired layout.

user_2082730

Compose handles nested layouts efficiently, making them a great way to design a complicated UI. This is an improvement from Android Views, where you need to avoid nested layouts for performance reasons.

from Android doc

user_4385040
Related