How does ConstraintLayout enable flat responsive UIs with chains and barriers?

WHAT THIS TESTS: Whether you understand that ConstraintLayout replaces deep view hierarchies with a flat constraint graph solved in a single pass, and whether you know the specific tools it provides for responsive behavior.

A GOOD ANSWER COVERS: First, the performance win of a flat hierarchy. Nested LinearLayouts trigger exponential measure passes in the worst case, while ConstraintLayout resolves constraints in one pass. Second, chains. A chain forms when views are linked by opposing constraints, such as view A's right edge constrained to view B's left edge and view B's left edge constrained back to view A's right edge. Chains support spread, spread inside, and packed modes with weights, letting a row of buttons distribute evenly across available width without nesting. Third, barriers. A barrier is a virtual reference line that moves to the most extreme edge of a referenced set of views. If one view in the set grows, the barrier shifts, and anything constrained to the barrier moves with it.

COMMON WRONG ANSWERS: Calling a chain just a LinearLayout inside ConstraintLayout misses the point that chains participate in the same constraint graph and avoid extra view groups. Using a barrier when a fixed guideline or simple end-to-start margin would work shows confusion about dynamism. Another red flag is claiming ConstraintLayout is always faster regardless of complexity; extremely dense constraint sets can still hurt performance.

LIKELY FOLLOW-UPS: How does ConstraintLayout performance compare to Compose? When would you use a guideline versus a barrier? How do you debug a broken chain where views collapse to zero size? What are the limitations of weighted chains in wrap_content scenarios?

ONE CONCRETE EXAMPLE: Imagine a form with a label and an EditText. If the label text is short, you want the EditText to start just after it. If the label is long in another language, you want the EditText to start after the longest label so inputs align vertically. Constrain the start of every EditText to a barrier that references all labels. The barrier automatically sits at the end of the widest label. For a chain example, imagine three action buttons in a dialog. Link them with opposing constraints in a horizontal chain set to spread evenly. They automatically divide the space without any LinearLayout parent.