Challenge 2: Why a Prototype's Search Doesn't Actually Filter Results — Solution Walkthrough

The answer:

Per this chapter's own warning box, this is expected, not a bug. A
Figma or Penpot prototype only simulates visual navigation between
pre-designed Frames — there's no real backend, no actual data
processing, and no genuine conditional behavior beyond whatever fixed
connections were manually set up.

Why typing a search term can't produce real filtered results:

Filtering real results based on arbitrary typed input would require
actual logic evaluating that input against real data — something no
design tool's prototyping feature is built to do. The prototype can
simulate tapping a specific, pre-defined search result to navigate
somewhere, but it cannot generically respond to whatever text a
stakeholder happens to type.

Why this is a deliberate, honest scope, not a missing feature:

Per this chapter's own material, prototyping exists to validate the
look, feel, and flow of an interface before development, not to
replace actually building the real, functioning product. A stakeholder
expecting genuine search functionality is expecting something outside
what a prototype was ever meant to provide.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that a prototype's inability to run real search
logic is correctly understood as an honest scope limitation, not a
defect in the prototype itself.