Property Search

Search rentals or properties by location, budget, bedrooms, amenities, availability, and commute preferences. This example brings Map and List together so property teams can find the next task without losing context.

It includes representative records such as 2BR · HSR Layout and 1BR · Indiranagar. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Property Search
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 results, new today and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Map gives users an obvious place to start.
  • Supporting view: List keeps the related context close.
  • Primary action: Save search stays visible when people need it.
  • First signal: Results shows a useful value (324).
  • Second signal: New today gives additional context (28).
  • Sample record: 2BR · HSR Layout.
  • Next record: 1BR · Indiranagar.

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

Map → List → Save search → Review outcome

Patterns used

Search, Map, List, 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 map and list. People need to distinguish 2BR · HSR Layout from 1BR · Indiranagar. 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 search”. Make error recovery as clear as the happy path.

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

Start from this in Figr

Design a property search screen inside our existing product. Use our current components, tokens and content language. Include Map and List views, credible records like 2BR · HSR Layout, 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