Travel Search

Search destinations, dates, travelers, stays, flights, and recommendations from one consumer travel experience. This example brings Explore and Stays together so travelers and booking teams can find the next task without losing context.

It includes representative records such as Tokyo · Oct 12–18 and Lisbon · Nov 3–8. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Use this template in Figr

Template facts

Screen

Primary action

Save trip search

Pattern

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to save trip search while keeping results, destinations and exceptions visible. The interface should show what changed and who should act next.

Key elements

Main workspace: Explore gives users an obvious place to start.
Supporting view: Stays keeps the related context close.
Primary action: Save trip search stays visible when people need it.
First signal: Results shows a useful value (1,284).
Second signal: Destinations gives additional context (62).
Sample record: Tokyo · Oct 12–18.
Next record: Lisbon · Nov 3–8.

States worth designing

No results: say what changed, protect progress, and offer a clear next step.
Filters return zero matches: say what changed, protect progress, and offer a clear next step.
Search taking longer: say what changed, protect progress, and offer a clear next step.
Results unavailable: say what changed, protect progress, and offer a clear next step.
Saved search ready: say what changed, protect progress, and offer a clear next step.
Restricted content omitted: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Explore → Stays → Save trip search → Review outcome

Patterns used

Search, Explore, Stays, contextual actions, error recovery

Why these choices work

Preserve query and filters when moving into results. Suggest useful recovery when the search returns nothing.

Pay attention to explore and stays. People need to distinguish Tokyo · Oct 12–18 from Lisbon · Nov 3–8. Keep results visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Save trip search”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Hotel Listing, Hotel Detail, Flight Search.

Start from this in Figr

Design a travel search screen inside our existing product. Use our current components, tokens and content language. Include Explore and Stays views, credible records like Tokyo · Oct 12–18, and a clear “Save trip search” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr