A phone is not the spare screen
A residential project site is usually presented to the client on a large monitor. The layout is approved, the renders look good, the availability grid looks the way it does in a strong project. Meanwhile the buyer is scrolling on a phone on the metro or the sofa. The developer is looking at one site; the buyer is looking at another.
Below is the order in which things usually break, roughly following the path a buyer takes.
1. The availability grid
The floor-by-section grid was designed for a large screen. On a phone it either shrinks into a small table whose cells a finger cannot hit, or gets cut into pieces that lose their meaning. Formats for the plans themselves are in interactive floor plans.
The fix is not a smaller grid. On a phone people begin from parameters: how many rooms, what budget, which floor. A list of cards with filters works better than a table, and the grid stays as a secondary view for those who care about location.
2. Floor plans
A plan drawn for a printed brochure becomes a smudge on a phone: room dimensions are unreadable and the legend is tiny. The usual remedy is pinch-zoom, but that is an extra action every single time.
Show what a phone can actually read: a large plan, room labels with areas, and a separate button that opens the drawing full screen. If the plan exists only as a PDF file, it is barely used on mobile at all.
3. Filters
On desktop the filters sit in a column and are always visible. On a phone they tend to cover half the screen or hide where nobody finds them. Two typical mistakes: the filter opens, but the results cannot be seen until it closes; and the reset is buried so a person cannot get back to the full list.
A good sign: the number of matching units is visible straight away, and the chosen conditions appear as a row above the list, each removable with one tap.
4. Renders, video and 3D
This is the heaviest part of the site. Full-resolution photoreal renders, background video, a 3D tour, a map, animation: on a good computer it all works, but on a mid-range phone over mobile data the page either loads slowly or stutters as you scroll.
The principle is simple: show heavy things on request. A poster frame instead of autoplay, the tour behind a button, images sized for the screen instead of files from the designer's archive. The beauty stays; the price is not that the visitor leaves before the first screen. Where the time goes and what to fix first is in website speed and buyer drop-off.
5. The enquiry form
On a narrow screen forms break more often than expected: the phone field opens a letter keyboard, the button slides under the keyboard, the confirmation after sending is out of view. Each extra field costs more here than on a computer, since typing on a phone is awkward. What to keep and how to confirm submissions actually arrive is in lead form conversion.
6. The call button and messenger
A phone is a screen where a call takes a single tap. A number that is not a call link is a missed chance, because the person has to copy digits. The same goes for messengers: the button should open a chat, not a page that describes one.
One more detail: the contact option should be reachable without scrolling to the footer. A pinned bar at the bottom of the screen solves it, provided it does not cover content or fight with the form.
How to check it in one evening
- Take a mid-range phone and switch wifi off.
- Walk the buyer path: find a unit within a budget, open its plan, send an enquiry.
- Note every place where you had to zoom, wait more than a few seconds or search for a button.
- Call the number on the site and send the form: confirm both actually arrive.
The list is usually short, and the first three items give most of the benefit. Our approach to this kind of site is on the real estate page.
