Property Detail

Review photos, rent, availability, amenities, rules, neighborhood context, and tour options for a property. This example brings Overview and Amenities together so property teams can find the next task without losing context.

It includes representative records such as South-facing balcony and Pet-friendly building. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Property Detail
Use this template in Figr

Template facts

Screen

Detail

Primary action

Schedule tour

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 schedule tour while keeping rent, beds 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: Amenities keeps the related context close.
  • Primary action: Schedule tour stays visible when people need it.
  • First signal: Rent shows a useful value (2,450).
  • Second signal: Beds gives additional context (2).
  • Sample record: South-facing balcony.
  • Next record: Pet-friendly building.

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 → Amenities → Schedule tour → Review outcome

Patterns used

Detail, Overview, Amenities, 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 amenities. People need to distinguish South-facing balcony from Pet-friendly building. Keep rent 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 “Schedule tour”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Property Search, Rental Application, Lease Management.

Start from this in Figr

Design a property detail screen inside our existing product. Use our current components, tokens and content language. Include Overview and Amenities views, credible records like South-facing balcony, and a clear “Schedule tour” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr