iProply

Type

Real estate property search platform

My role

Developer

Stack

Core PHP, MySQL, JavaScript

Live

iproply.com

The problem

Property portals fail in a specific way. Someone arrives wanting a three-bedroom house to rent in a particular neighbourhood under a certain price. If reaching that set takes more than a few interactions, they leave — not because the inventory was wrong, but because finding it was work.

The second problem is the handoff. A visitor who finds the right property still has to reach a human. If that path is unclear, the search was wasted effort for everyone involved.

My approach

Put the search itself in the hero, not behind a menu. The homepage leads with a search panel covering the four criteria people actually use — location, property type, buy or rent, and price range — plus a location detection option so mobile visitors can skip typing an address entirely.

Alongside it, two clear paths: browse properties for people who want to look around, and talk to an agent for people who already know what they want. Different intents, different buttons, no forcing everyone down one funnel.

What was built

Multi-criteria property search

Search by city, address, ZIP or neighbourhood, filtered by property type, buy-or-rent status and minimum and maximum price — with current-location detection as a shortcut.

Property listings

A structured listings section covering homes, condos and commercial spaces, presented consistently so comparison between properties is straightforward.

Agent directory and contact routing

An agents area plus direct "talk to an agent" paths, so a visitor can reach a person at any point rather than only at the end of a search.

Partnership programme and company pages

Supporting sections — partnership programme, company information and resources — that give the platform credibility with both consumers and the agents it depends on.

Accounts and live chat

Sign-in and registration for returning users, with a live chat widget for visitors who would rather ask a question than fill in a form.

Technology

Language

Core PHP (no framework)

Database

MySQL

Front end

JavaScript, responsive CSS

Patterns

Search & filter queries, listing templates

Features

Accounts, agent directory, live chat

Focus

Search speed, mobile usability

This one is built in core PHP rather than a framework. That is a constraint worth naming honestly: it means the query and templating layers are hand-rolled, so the discipline has to come from how the code is organised rather than from a framework enforcing it. Indexing the columns the search actually filters on matters much more here than it would in an ORM-backed project.

Problems solved

• Relevant properties reachable in a few interactions from the homepage
• Mobile visitors able to search by current location instead of typing an address
• Separate paths for browsing versus speaking to an agent
• Consistent listing presentation across homes, condos and commercial spaces

Results

Placeholder — needs verified data. No performance figures are published here yet. Once you have something you can evidence — analytics screenshots, CRM exports, a written client confirmation — add it in this block. Unverifiable numbers on a portfolio are worse than none: one sharp client question and the whole page loses credibility.