A second, separate site for Indus Real Estate's premium listings. Access is restricted to registered users.
Built against the opposite goal
The main Indus site is built to be found. Search rankings, indexable listing pages, fast first paint for people arriving from Google.This one is built not to be. Owners of high-value properties often do not want their address, interior photographs and asking price publicly indexed, and buyers at that level are introduced by an agent rather than arriving from a search result. So the requirements invert: registration ahead of any listing detail, nothing indexable, and no public entry point into the inventory.Building the two as one site with a permission flag would have been a mistake. The caching, the rendering strategy and the metadata all want to be different, and a single codebase serving both intentions tends to leak the private half into the public one eventually.
Interface
Because there is no search traffic to optimise for, the interface could be slower and heavier in the places where that buys something: larger photography, more space, fewer listings on screen at once. The result is closer to a brochure than to a search tool, which suits both the inventory and the audience.Next.js on the front with PHP and Node.js behind it over SQL, sharing the property data model with the main site.
Screens
Related projects
Indus Real Estate, public property site
A rebuild of a Dubai real estate agency's public site that cut page load time by 70 percent, measured on first contentful paint.
A gamified training platform for Abbott's medical reps
A CRM where trainers build realistic sales scenarios, and a game where more than 1,000 medical representatives play through them against a live leaderboard.