Challenge 3: Navigate To vs. Open Overlay — Solution Walkthrough

The answer:

Per this chapter's own material, Navigate To jumps fully to a
destination Frame, replacing the current screen entirely. Open Overlay
instead shows a Frame layered on top of the current screen, without
fully replacing it — the original screen stays present underneath.

A real interface example for Navigate To:

Tapping a product in a list and moving to that product's own full
detail screen fits Navigate To well — the user has genuinely moved to
a new, distinct screen, and the previous list screen is no longer the
active view.

A real interface example for Open Overlay:

Tapping a "..." menu button to reveal a small dropdown of options, or
tapping a button that opens a confirmation modal, fits Open Overlay
well — the underlying screen is still visible and still relevant, just
temporarily covered by the overlay content until it's dismissed.

Why this distinction matters practically:

Choosing the wrong action would misrepresent how the real app is
actually meant to behave — using Navigate To for what should be a
quick dropdown menu would make the prototype feel like it fully left
the current screen, when a real implementation would just show a small
layered element instead.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that Navigate To and Open Overlay are correctly
distinguished by whether the current screen is fully replaced or
merely layered over, with a plausible real-world example for each.