Flight Search

Compare routes, airlines, stops, fare classes, flexible dates, baggage, and total flight prices. This example brings Flights and Flexible dates together so travelers and booking teams can find the next task without losing context.

It includes representative records such as BLR → NRT · Singapore Air and BLR → NRT · Thai Airways. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Flight Search
Use this template in Figr

Template facts

Screen

Search

Primary action

Track prices

Pattern

Search

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to track prices while keeping flights, lowest fare and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Flights gives users an obvious place to start.
  • Supporting view: Flexible dates keeps the related context close.
  • Primary action: Track prices stays visible when people need it.
  • First signal: Flights shows a useful value (148).
  • Second signal: Lowest fare gives additional context (612).
  • Sample record: BLR → NRT · Singapore Air.
  • Next record: BLR → NRT · Thai Airways.

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

Flights → Flexible dates → Track prices → Review outcome

Patterns used

Search, Flights, Flexible dates, 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 flights and flexible dates. People need to distinguish BLR → NRT · Singapore Air from BLR → NRT · Thai Airways. Keep flights 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 “Track prices”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Hotel Detail, Travel Booking Checkout, Hotel Listing.

Start from this in Figr

Design a flight search screen inside our existing product. Use our current components, tokens and content language. Include Flights and Flexible dates views, credible records like BLR → NRT · Singapore Air, and a clear “Track prices” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr