Case Study · Apartments.com · CoStar · Homes.com · Mortar
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.
The challenge
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.
System principles
The architecture focused on separating foundational system behavior from brand-level presentation and theming.
This allowed products to share:
while maintaining flexibility in:
Building flexible theming
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.
Consumer experience systems
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.
Frontend implementation
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.
Adapting to platform growth
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.
Outcomes
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.
Long-term impact
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.
Other projects
Indeed
Embedded product infrastructure: tooling, automation, and observability that scaled adoption while keeping teams aligned with central standards.
Read case studyIndeed
Multi-platform architecture: semantic tokens, scalable theming, and governance that scaled adoption across hundreds of teams.
Read case studyIndeed
Evolving the design system for conversational and generative AI: interaction primitives and workflow architecture across hiring products.
Read case study