What problem does IntrinsicWidth solve and what are its performance costs?

What's really being asked

This question probes whether you understand Flutter's two-phase layout protocol and the difference between constraints and intrinsic dimensions. Interviewers want to see that you know IntrinsicWidth is not a generic sizing helper but a specialized escape hatch for situations where a child must know its own ideal width before the final layout pass.

The full answer

First, the problem it solves. When a parent offers unbounded width, a child like a Row or text might try to expand forever. IntrinsicWidth caps the child at its maximum intrinsic width, which is the width the child would prefer if height were unconstrained. Second, the Column trick. Wrapping a Column inside IntrinsicWidth forces all children to share the width of the widest sibling because the Column receives tight width constraints derived from that widest child. Third, constraint passthrough. The widget still respects the parent's constraints, so if the max width is smaller than the intrinsic width, the child gets less; if the min width is larger, the child gets more. Fourth, performance. IntrinsicWidth triggers a speculative layout pass before the real layout phase. In the worst case this creates O(N²) complexity relative to tree depth because every speculative pass can recurse down the tree. You should avoid it where possible.

The mistakes people make

Saying it simply makes a child wrap its content without mentioning the speculative pass. Claiming it is cheap or using it as a default way to align buttons. Confusing intrinsic width with final width or ignoring the interaction with parent constraints. Another red flag is suggesting it inside deeply nested lists or scrolling containers where the layout cost multiplies.

What usually comes next

How would you achieve the same Column alignment without IntrinsicWidth? The expected answer is to use a shared widget or measure text with TextPainter outside of layout. What happens if you place IntrinsicWidth inside a ListView? The interviewer wants to hear that scrolling widgets provide unbounded constraints, so the combination can cause expensive layouts and potential jank. Can you explain the difference between getMinIntrinsicWidth and getMaxIntrinsicWidth? A senior candidate should note that max intrinsic width is the width needed when height is unconstrained, while min intrinsic width is the narrowest width the child can tolerate.

A concrete example

Imagine a dialog with a Column of ElevatedButtons where each button has different text. Without IntrinsicWidth, the buttons size to their own text and look ragged. Wrapping the Column in IntrinsicWidth makes every button as wide as the longest label. However, if the dialog contains twenty such columns in a ListView, each IntrinsicWidth call triggers a speculative pass, turning layout into an N squared nightmare. The better solution is to give every button a fixed minimum width or compute the longest label once and apply it via a SizedBox or ConstrainedBox.