Address Book

Manage saved delivery and billing addresses with default selection, validation, labels, contact details, and recent use. This example brings Addresses and Defaults together so shoppers can find the next task without losing context.

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

Address Book
Use this template in Figr

Template facts

Screen

Settings

Primary action

Add address

Pattern

Settings

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Finance and operations teams need to add address while keeping saved, default and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Addresses gives users an obvious place to start.
  • Supporting view: Defaults keeps the related context close.
  • Primary action: Add address stays visible when people need it.
  • First signal: Saved shows a useful value (4).
  • Second signal: Default gives additional context (Home).
  • Sample record: Home · HSR Layout.
  • Next record: Office · Koramangala.

States worth designing

  • Default preferences: say what changed, protect progress, and offer a clear next step.
  • Unsaved changes: say what changed, protect progress, and offer a clear next step.
  • Policy blocks edit: say what changed, protect progress, and offer a clear next step.
  • Changes applied: say what changed, protect progress, and offer a clear next step.
  • Restricted settings: say what changed, protect progress, and offer a clear next step.
  • Connectivity interrupted: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Addresses → Defaults → Add address → Review outcome

Patterns used

Settings, Addresses, Defaults, contextual actions, error recovery

Why these choices work

Separate safe everyday choices from risky changes, show who can edit them, and confirm irreversible actions.

Pay attention to addresses and defaults. People need to distinguish Home · HSR Layout from Office · Koramangala. Keep saved 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 “Add address”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Wishlist, Delivery Options, Shopping Cart.

Start from this in Figr

Design a address book screen inside our existing product. Use our current components, tokens and content language. Include Addresses and Defaults views, credible records like Home · HSR Layout, and a clear “Add address” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr