Hotel Detail

Evaluate a stay through rooms, amenities, policies, reviews, location, availability, and total trip pricing. This example brings Overview and Rooms together so travelers and booking teams can find the next task without losing context.

It includes representative records such as Deluxe king · city view and Twin room · breakfast. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Hotel Detail
Use this template in Figr

Template facts

Screen

Detail

Primary action

Reserve room

Pattern

Detail

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to reserve room while keeping nightly, rating and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Overview gives users an obvious place to start.
  • Supporting view: Rooms keeps the related context close.
  • Primary action: Reserve room stays visible when people need it.
  • First signal: Nightly shows a useful value (184).
  • Second signal: Rating gives additional context (4.7).
  • Sample record: Deluxe king · city view.
  • Next record: Twin room · breakfast.

States worth designing

  • Record not available: say what changed, protect progress, and offer a clear next step.
  • Details refreshing: say what changed, protect progress, and offer a clear next step.
  • Incomplete evidence: say what changed, protect progress, and offer a clear next step.
  • Action complete: say what changed, protect progress, and offer a clear next step.
  • Record read-only: say what changed, protect progress, and offer a clear next step.
  • History not available: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Overview → Rooms → Reserve room → Review outcome

Patterns used

Detail, Overview, Rooms, contextual actions, error recovery

Why these choices work

Emphasize record status, next action and recent changes. Put secondary history nearby without competing with the primary task.

Pay attention to overview and rooms. People need to distinguish Deluxe king · city view from Twin room · breakfast. Keep nightly 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 “Reserve room”. Make error recovery as clear as the happy path.

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

Start from this in Figr

Design a hotel detail screen inside our existing product. Use our current components, tokens and content language. Include Overview and Rooms views, credible records like Deluxe king · city view, and a clear “Reserve room” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr