Split search
Buy / Rent toggle before city, type and budget.
Design note
The first decision splits the audience. Everything downstream — language, filters, proof points — changes based on this one toggle.
Real Estate
Nestora
Find a home you'll love living in.
A property platform for Indian families — RERA-verified listings, zero brokerage on select homes, and three distinct journeys for buying, renting and selling.
Visit the live siteapldigital.in/real-estate
Open ↗Loading Nestora…
Role
Designer & Front-end Developer
Timeline
Feb – Aug 2025
Scale
5 pages
Built with
React · Tailwind · Supabase · Framer Motion
5
Pages, fully functional
42+
Cities in the browse system
3
Distinct user journeys
The problem
Indian property portals funnel three completely different users — buyers, renters and sellers — through one generic search bar, then bury all of them in unverified listings and undisclosed brokerage. The experience treats a ₹6.5 crore purchase and a ₹55,000 rental as the same task.
The approach
I split the journey at the very first interaction. Buy, Rent and Sell each get their own three-step path with its own language, its own proof points and its own CTA. Verification status and zero-brokerage sit on the listing card itself, not in the fine print.
What shipped
A five-page platform with property-type and city browsing, a full listing detail system, RERA-certified agent profiles, and three separate guided journeys that never collide.
Process
How it came together
Journey split
Mapped buyer, renter and seller tasks side by side and found almost no shared steps beyond the property object itself.
Trust placement
Moved every verification signal from policy pages onto the cards where evaluation actually happens.
Numeric type scale
Tuned the type system around price and area legibility at card density, since those drive the scan.
Build
Shipped browse by type and city, listing detail, agent profiles and all three journeys across five pages.
Design system
Colour & type
Colour system
Ink
#121216
Headings & base
Nestora Green
#1AA87D
Brand, verified & primary action
Deep Green
#127356
Hover & pressed
Mint
#E7F9F3
Verified badge backgrounds
Zinc
#71717A
Property metadata
Amber
#F59F0A
Featured listing badges
Typography
Display
Aa
Inter — Bold
Body
Aa
Inter — Regular / Medium
Numbers do the heavy lifting here — price, sqft, BHK, EMI. The type scale was tuned around numeric legibility at card size rather than around headlines.
Key screens
What each screen has to do
Listing card
Price, BHK, sqft, furnishing and verification on one card.
Design note
RERA status sits on the card, not the detail page. If verification is the differentiator it cannot require a click to discover.
Property spotlight
A full-bleed featured listing with amenities and specs.
Design note
Premium inventory needs room. The spotlight gives one property the space a ₹6.5 crore listing actually warrants.
Three journeys
Buy, Rent and Sell as separate three-step paths.
Design note
A seller and a renter share no vocabulary. Giving each its own path removed every compromise the shared flow was forcing.
Design decisions
What got cut, and why
Search entry
Rejected
One universal search bar with buy/rent as a filter applied afterwards.
Shipped
Buy / Rent chosen first, changing the entire downstream experience.
Why
Buying and renting share almost no criteria. Treating the difference as a filter forces both users through a compromise built for neither.
Trust signals
Rejected
A trust page listing RERA compliance and verification policy.
Shipped
Verified, RERA and zero-brokerage badges on every listing card.
Why
Trust has to arrive at the moment of evaluation. A separate page is read by nobody who was not already convinced.
Seller flow
Rejected
Fold selling into the same listing flow with a role switch.
Shipped
A distinct Sell journey opening with a free valuation offer.
Why
Sellers arrive with a different question — what is it worth — and answering that first is what earns the listing.
What I owned
Multi-path searchListing detail systemAgent profilesBuy / rent / sell journeys
It's live. Go use it.
Every screen described here runs in production — real routing, real data, real interactions.
Open NestoraNext up
Drape