yeah, but if I have a view, which has an ID, but is not used in the activity, for example I need a Relative layout construct

f.babic: Use ConstraintLayout instead of RelativeLayout, it's more efficient (only one layout pass, versus 2 on RelativeLayout for same effect)

That’s not towards his question, and many of us still feel that the

ConstraintLayout

isn’t ready for production apps yet

what if I don’t like constraint ^^ and the design we receive in projects is fully custom, so constraint can’t cover it

@brianwernick That's why I put it in a thread. ConstraintLayout is ready for production apps, just like Android is, but can't tell it covers all RelativeLayout use cases, sure...

generally the problem would be migrating legacy projects or even starting the new ones in Kotlin, without having to change the complete conventions our team uses