Property listing platform
Atlas Properties
A bilingual property portal: 1,240 listings, faceted search and an agent-facing CMS.
Concept buildThe work
About the build
Search state lives in the URL, so a filtered view can be shared, indexed and reached with the back button. The results page renders on the server; only the filter bar runs in the browser.
Arabic is a direction, not a second site — one component tree flips from the route. When an agent edits a price, a webhook refreshes the three pages it touches and leaves the rest alone.
The listing, in Arabic
The same component tree, mirrored from the route — not a second site with its own bugs.
Measured
What it does under test
- LCP on a filtered results page
- 0.9s
- Lighthouse performance
- 100
- Build of 1,240 pages
- 47s
Lighthouse on mobile emulation, median of five runs, measured on CI against synthetic listings.
Stack
What we used
- Next.js
- TypeScript
- Strapi
- PostgreSQL
- Typesense
Concept build — engineered in-house
Similar scope
What a build at this scope involves
A portal with faceted search, an editor console and two languages is a system build, not a website.
- Search and language decided before design
- Editor console demoed before the public site
- Schema documented, whole repository handed over
More work
The other two builds
Clinic booking system
Nadra Clinics
A four-branch booking system with held slots, WhatsApp confirmations and a front-desk console.
Read the buildE-commerce storefront
Soukone
An AED storefront with card and instalment payments, VAT-correct invoices and a steady checkout.
Read the build
Planning a listing platform?
Search, the CMS and language are the three decisions that set the cost of everything after them.