Case Study
Regal Home — Designing a multilingual real estate platformHow I designed and helped build a real estate product with property discovery, project pages, map-based search, multilingual content and admin workflows.
- Product Design
- Real Estate
- Multilingual UX
- AI-assisted Development
- Role
- Product Designer, UX/UI, Product Strategy, AI-assisted product development
- Industry
- Real Estate / Property Marketplace / Digital Platform
- Scope
- Property listings, project pages, map search, filters, property submission flow, admin panel, multilingual experience, inquiry flow, favorites and comparison
- Tools
- Figma, Next.js, Supabase, Product strategy, UX architecture, AI-assisted development, Multilingual content structure
01 · Overview
The short version
Regal Home was designed as a modern real estate platform for discovering properties, projects and real estate opportunities through a clean multilingual experience. The product included public listing pages, property detail pages, project pages, map-based discovery, filters, favorites, comparison, inquiry flows and an admin system for managing content and submissions. I worked on the product direction, UX structure and AI-assisted development process, helping turn the idea into a functional real estate platform with both public-facing discovery and internal management workflows.
02 · Context
Where it started
Real estate websites often need to serve two very different user groups: people searching for properties and teams managing property data behind the scenes. For Regal Home, the challenge was to create a product that felt simple for buyers and renters while still giving the internal team enough structure to manage properties, projects, inquiries, submissions and multilingual content. The platform also needed to support Armenian, English and Russian audiences, making content structure and localization an important part of the product experience.
03 · Problem
What was broken
The main challenge was designing a real estate product that could support property discovery, trust-building and internal operations without becoming too complex.
- Users needed fast ways to search, filter and compare properties.
- Property detail pages needed to present information clearly and convincingly.
- The platform needed project pages for larger real estate developments.
- Map-based discovery had to support location-driven browsing.
- Admin workflows needed to make property and project management easier.
- Multilingual content had to work across Armenian, English and Russian.
- Inquiry and submission flows needed to connect public users with the business team.
04 · My Role
Where I stood
I worked across product strategy, UX/UI, information architecture and AI-assisted product development. My role included structuring the public website experience, thinking through listing and project flows, shaping admin workflows, supporting multilingual content logic and helping define how users would discover, compare and inquire about properties. This was not only visual UI work — it was product architecture, marketplace UX, admin UX and product-building work.
05 · Team & Tools
How it was staffed
- Team
- [FILL: client / developer / product collaborators / team size]
- Timeline
- [FILL: month/year — month/year]
- Tools
- Figma, Next.js, Supabase, Product strategy, UX architecture, AI-assisted development, Multilingual content structure
06 · Constraints
What shaped the approach
- The product had to support both public users and internal admins.
- Property data needed to be structured enough for filtering, comparison and detail pages.
- The platform needed to work across multiple languages.
- Real estate content had to feel trustworthy and visually clear.
- Admin workflows needed to be practical for non-technical users.
- The product had to balance rich property information with a clean browsing experience.
- Map, filters, favorites and comparison features needed to work as one discovery system.
07 · Process
How it moved
Product structure
I started by defining the core product areas: property discovery, property detail pages, project pages, map search, user actions, inquiries, submissions and admin management.
Discovery UX
I structured the property browsing experience around filters, grid/list/map views, search behavior, favorites and comparison so users could move from exploration to shortlist.
Property detail logic
I worked on the structure of detail pages so users could understand the property, view key information, explore visuals and take action through inquiry flows.
Project pages
I designed the logic for real estate project pages, separating individual properties from larger developments and making project-level information easier to browse.
Admin workflows
I helped structure the admin experience for managing properties, projects, blog content, inquiries, submissions and advisor-related information.
Multilingual content
The product needed Armenian, English and Russian versions, so content fields, routing and page structure had to support localization without breaking the experience.
AI-assisted development
AI tools were used to accelerate implementation planning, structure product logic, generate code support and move faster from product decisions to working features.
08 · Key Decisions
Choices that mattered
Design the platform around discovery, not only listings.
Why: Real estate users need to explore, filter, compare and build confidence before making contact.
Separate properties and projects.
Why: A single property listing and a real estate development project require different information structures and browsing behavior.
Include map, grid and list discovery modes.
Why: Real estate decisions are strongly location-driven, but users also need fast visual scanning and structured comparison.
Build admin workflows as part of the product, not an afterthought.
Why: A real estate platform only stays useful if the internal team can manage content, inquiries and submissions efficiently.
Treat multilingual support as a product requirement from the start.
Why: Armenian, English and Russian audiences need consistent access to property information without duplicated or broken content structures.
Use AI-assisted development to speed up product delivery.
Why: AI helped move faster from UX/product decisions to implementation, but the core product logic still needed human direction, review and iteration.
09 · Solution
What we built
The result was a multilingual real estate platform with structured property discovery, property and project detail pages, map-based browsing, filters, favorites, comparison, inquiry flows and an admin system for managing real estate content and operations.
- Property discovery experience
- Property detail pages
- Real estate project pages
- Map, filters, favorites and comparison
- Inquiry and property submission flows
- Admin panel and content management
- Multilingual structure
- AI-assisted product development workflow
10 · Product UX
Designing for the team
The UX work focused on making real estate discovery easier, clearer and more actionable. Users needed to quickly understand what a property offers, compare options and decide whether to contact the team.
- Search and filter logic for property browsing.
- Grid/list/map discovery modes.
- Structured property detail pages.
- Project pages for real estate developments.
- Favorites and comparison for shortlisting.
- Inquiry flows connected to property/advisor context.
- Admin workflows for managing listings and inquiries.
- Multilingual content architecture.
11 · Impact
What changed
Regal Home created a stronger digital foundation for presenting properties, managing real estate content and connecting interested users with the business team. The product brought public discovery and internal management into one platform, making the real estate experience more structured, scalable and easier to maintain.
- [FILL: number of property listings added]
- [FILL: number of real estate projects added]
- [FILL: number of inquiries received]
- [FILL: number of languages supported]
- [FILL: number of admin workflows created]
- [FILL: launch or production status]
12 · Visuals & Artifacts
Supporting material
13 · Key Learnings
What I keep
- This project reinforced that marketplace-style products need both strong public UX and strong internal workflows. A real estate platform is not only about attractive listing pages — it also needs structured data, content management, inquiry logic and trust-building patterns.
- The biggest lesson was that discovery and operations have to be designed together. Users need a simple way to explore properties, while the internal team needs a reliable system to keep listings, projects and inquiries organized.