Challenge 3: Why Nested Frames Reflect Real Interface Structure — Solution Walkthrough

The answer:

Per this chapter's own material, real interfaces are built from
smaller, reusable pieces rather than one flat, unstructured canvas — a
screen is made up of lists, which are made up of individual cards,
each card containing its own smaller elements. Nesting a card Frame
inside a list Frame inside a screen Frame mirrors that exact
real-world structure directly in the design tool.

Why this isn't an arbitrary organizational preference:

An actual coded interface is built the same way — components
containing components, nested according to how the interface is
genuinely composed. Matching that same nested structure in the design
file means the design's own organization maps naturally onto how a
developer will eventually need to build it, rather than being an
arbitrary grouping choice made purely for the designer's own
convenience.

Why this connects forward in this course:

This nested structure becomes especially useful once Chapter 4's Auto
Layout is applied at each level — a card's own internal spacing, a
list's own spacing between cards, and a screen's own overall layout can
each be controlled independently, precisely because they're organized
as separate, nested Frames rather than one undifferentiated canvas.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that nested Frames are correctly understood as
mirroring genuine interface structure, not just a convenient but
arbitrary way of grouping shapes.