Hotel Listing

Compare hotels through price, rating, location, amenities, availability, and map or list browsing. This example brings Results and Map together so travelers and booking teams can find the next task without losing context.

It includes representative records such as Kumo Hotel Shinjuku and Casa Alfama Lisbon. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Hotel Listing
Use this template in Figr

Template facts

Screen

Search

Primary action

Save search

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 save search while keeping stays, avg nightly and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Results gives users an obvious place to start.
  • Supporting view: Map keeps the related context close.
  • Primary action: Save search stays visible when people need it.
  • First signal: Stays shows a useful value (326).
  • Second signal: Avg nightly gives additional context (184).
  • Sample record: Kumo Hotel Shinjuku.
  • Next record: Casa Alfama Lisbon.

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

Results → Map → Save search → Review outcome

Patterns used

Search, Results, Map, 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 results and map. People need to distinguish Kumo Hotel Shinjuku from Casa Alfama Lisbon. Keep stays 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 search”. Make error recovery as clear as the happy path.

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

Start from this in Figr

Design a hotel listing screen inside our existing product. Use our current components, tokens and content language. Include Results and Map views, credible records like Kumo Hotel Shinjuku, and a clear “Save search” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr