← Back to home

Case Study · Apartments.com · CoStar · Homes.com · Mortar

Building a multi-brand experience system across consumer real estate platforms

Designing a scalable frontend and design system architecture that supported Apartments.com, CoStar, and Homes.com while enabling brand flexibility, shared implementation patterns, and rapid product expansion.

Design system architecture Multi-brand theming Consumer experience systems Frontend foundations Scalable implementation

Supporting multiple brands without fragmenting the platform

The platform ecosystem included multiple consumer-facing real estate products with overlapping functionality but distinct brand identities, audiences, and business goals.

The challenge was balancing:

with:

Without a shared system strategy, products risked:

The goal was creating a flexible system foundation capable of supporting multiple brands and workflows without requiring separate frontend ecosystems for each product.

Shared foundations with adaptable presentation layers

The architecture focused on separating foundational system behavior from brand-level presentation and theming.

Foundations

  • System behavior shared across products

Presentation

  • Brand-level theming and expression

This allowed products to share:

while maintaining flexibility in:

System emphasis Reuse without uniformity; scalability without rigidity.

Designing a scalable theming architecture

The theming model introduced reusable styling foundations capable of adapting across multiple consumer brands.

Rather than hardcoding visual decisions directly into components, the system used layered styling and semantic abstractions that allowed presentation changes without rewriting core functionality.

This supported:

The architecture made it possible to adapt interfaces across Apartments.com, Homes.com, and broader CoStar product initiatives while preserving shared implementation foundations.

Designing for high-volume consumer workflows

Unlike internal enterprise systems, consumer real estate platforms required interfaces optimized for:

The system needed to support:

This required balancing:

across rapidly evolving product surfaces.

Bridging design systems and production workflows

A major focus was ensuring the system worked effectively inside real implementation environments.

The system introduced:

This improved:

The architecture reduced duplication while allowing product teams to continue evolving experiences independently.

Supporting evolving business and product needs

As the platform ecosystem expanded, the system needed to accommodate:

The system was intentionally designed for adaptability rather than fixed implementation.

This allowed teams to:

The architecture supported long-term platform scalability rather than short-term feature delivery alone.

Scalable frontend consistency across multiple brands

The system established shared frontend foundations that improved consistency and implementation efficiency across consumer-facing real estate platforms.

Key outcomes included:

The architecture enabled product teams to move more efficiently while preserving the flexibility required for distinct brand and product experiences.

From isolated interfaces to scalable product infrastructure

The most important shift was moving from independently implemented interfaces toward a shared experience architecture capable of supporting long-term platform evolution.

The work established:

The result was a more durable product ecosystem capable of supporting multiple brands, workflows, and evolving consumer experiences without fragmenting the underlying platform architecture.

Read more case studies