Challenge 3: Preview Pane vs. Launching the Emulator — Solution Walkthrough

Why the Preview pane is generally faster:

Per this chapter's own material, the Preview pane can render a layout
across multiple screen sizes, orientations, themes, and API levels
side by side without ever running the app on a device or emulator at
all. Launching the emulator (Chapter 6) means booting a full virtual
device, installing the app onto it, and launching the app itself —
real overhead that has to happen before the layout can even be seen —
whereas the Preview pane renders directly from the layout file itself,
skipping all of that.

What checking multiple configurations in Preview actually confirms:

It confirms how the layout itself renders and positions its views
across different screen dimensions and settings — a fast, useful check
specifically for layout and visual correctness.

What this doesn't replace:

Per this chapter's own framing, the Preview pane is "a time-saver," not
a full replacement — it doesn't run any of the app's actual code,
verify real user interaction/behavior, or catch issues that only
appear when the app is genuinely running (performance problems, actual
touch handling, real data being loaded). Confirming the app behaves
correctly, not just that the layout looks right, still requires
actually running it on the emulator or a real device at some point.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that the Preview pane's own speed advantage is
understood as coming from skipping the emulator's boot/install/launch
overhead specifically for layout checks, while still recognizing this
chapter's own point that it complements, rather than replaces, actually
running the app.