Low-fidelity wireframes for the 4 screens named in the PRD's "Design — Key Flows" section —
intentionally boxy and grayscale, since this is a wireframe fidelity level, not a finished UI.
Scope note: these are the P0 requirements only (destination intent, itinerary
generation, budget optimizer) — see the
full PRD (T2)
for the Requirements table, Goals & Non-Goals, and Launch Plan these screens map to.
Screen 1
Intent Capture
Maps to: G1 (<90s to first itinerary)
Wayfare AI
Hi! Where are we planning your next trip?
"5 days in Vietnam under ₹60k, relaxed pace..."
Budget: ₹60k5 daysRelaxed
Plan my trip →
One input, not a form — free text + 3 quick-pick chips, no 12-field intake.
Chips pre-fill from parsed intent, editable before submit.
"Why this?" 4.6★ (2,100 reviews), closest highly-rated option to your hotel, within budget band.
Day 2 — Ha Long Bay
Day cruise + kayak₹3,200 · 4.7★
Swap, don't regenerate — tapping a card offers alternatives, not a full re-roll.
"Why this?" expand is the trust-layer requirement — reasoning is always one tap away.
Screen 3
Budget Bar
Maps to: G3 (swap without manual recalculation)
Budget
₹42,300 spentof ₹60,000
Itinerary items
Flight DEL↔SGN₹18,400
Hotel · 3 nights₹9,800
Ha Long Bay cruise₹3,200 → swapping...
Sticky, always visible — never buried in a separate summary screen.
Updates live on swap — no "recalculate" button, no wait state.
Screen 4
Book / Hold
Maps to: G2 (North Star — booked leg conversion)
Ready to Book
Flight DEL↔SGN₹18,400Booked
Hotel · 3 nights₹9,800Book
Ha Long Bay cruise₹3,200Book
Hold full itinerary (15 min)
Per-leg deep links — each item books independently, not an all-or-nothing checkout.
"Hold" reduces abandonment for an indecisive high-intent user (same pattern as Rec #5 in the Flight Booking Teardown, T1).
Reading it: only Screens 1–3 are P0/MVP — the destination intent, itinerary
generation, and budget optimizer requirements. Screen 4 (Book/Hold) reads as a natural
conclusion but its per-leg booking links depend on integrations outside this PRD's scope,
which is exactly the kind of dependency the Launch Plan's phasing exists to surface.