Vantage: how it came together.
How it came together.
- 01
The map, then the marketplace
Vantage was map-led through the summer of 2026: it opened on a map, and the first question it answered was what had been scanned near you. Checked 2026-09-11, the front door is a redirect to the marketplace instead, with the standalone full-screen map removed and the scan map folded into the scan library. Search stayed in plain language.
Product Strategy - 02
Reusing the shipped viewer, not forking one
The scan viewer ran on gaussian-splats-3d, shared with the standalone Splat Viewer through the barnes-scan-viewer package and embedded per residence, so a listing dropped you straight into the full walk rather than a second app.
3D & Spatial A scan ships only if it passes. Coverage, collision and a spawn point computed from the room's own geometry, checked against a written standard before a client ever opens it. - 03
An internal standard before a scan ships
Every scan was checked against a written internal standard (coverage, collision, a spawn point computed from the room's geometry) before it earned a Verified by Vantage badge. A point-cloud minimap replaced floor plans, which misread furniture as walls.
3D & Spatial - 04
Co-browse over a self-hosted relay
A broker drove the tour; the client's browser followed over a self-hosted WebSocket relay, not a third-party vendor. Verified live: join, presence, camera state, and reactions round-tripped correctly.
Backend Engineering - 05
Design matters because trust is visual
The register is a printed property dossier: an ivory ground, ink type, brass detailing and one Caslon cut carrying display and body, with figures in Fragment Mono so prices line up in a column. Light is the default and dark is a second real theme rather than an inversion, which is how the map view comes to be the dark one most buyers meet. A brokerage surface in front of a buyer has to read as finished.
Decisions on the record.
The few calls worth defending. Each one is a fork; the other branch would have been a different project.
Collapsing three broker apps into one surface
One surface with modes rather than three separate apps, so the listing a broker shows and the residence they walk are the same object, one click apart. That surface was the map until the summer of 2026, then the marketplace (checked 2026-09-11). The rebuild made the living map of Dubai the front door again, with each home and its walkthrough reached from it.
A self-hosted relay for co-browse
A broker-led tour needs low-latency camera sync between broker and client, but that traffic doesn't need to leave infrastructure already hosting the scans. A self-hosted WebSocket relay, co-located with the splat viewer, avoids a recurring realtime-vendor bill and keeps the stack in one place to operate.
The design system.
Tokens and treatments as they exist in the repo: values verbatim, nothing aspirational.
A calm frame around real homes standing in a model of the city. Pages are light; the map, the tour and the scan viewers are dark. One loud colour, Harbour Blue, marks what you can walk or press. No theme toggle, and no gold anywhere.
--vt-base#F5F5F7 / #0B0D0F- Page ground, light pages and dark viewers.
--vt-text-1#1D1D1F / #F5F5F7- Headings and body text.
--vt-loud#0A66D8- Harbour Blue, the one loud colour, with white text in both themes. One primary action per screen, walkable markers, the loader hairline and the active underline. A screen with no blue fill is fine.
--vt-accent#0A66D8 / #3D8BFF- Links, markers, focus rings and active states; the lighter blue is for dark viewers.
--vt-success / --vt-error#1A7F37 / #D70015- Status only, always with an icon and a word.
- Everything
AaBb Handgloves 0123
InterSelf-hosted, weights 400 to 700. Headings 600, labels and buttons 500, body 400. No light weights, sentence case, tabular figures in rows of numbers.
CSS custom properties named --vt-* in app/globals.css, defined once for light and once for dark, with tailwind.config.js carrying the Tailwind names. The canvas code cannot read CSS variables, so it takes the same values from lib/design-tokens.ts. Every older colour name is an alias onto these, so nothing can paint gold, and a token lint fails the build on any colour in the gold hue band.
- Radius
8px on controls, 12px on cards, 18px on sheets; capsule buttons; full round on markers.
Soft enough to read as one family with the device it runs on.
- Glass
Blur 20px and saturate 180%, only over the live scene or a picture.
Never on flat ground and never nested.
- Contrast
Every text token passes 4.5:1 on its ground in both themes, measured on 11 November 2026.
Pairs that fall short on a raised dark surface are kept off it, by rule.
- The twin
Full colour, no filter, opening bright at 15:00 Dubai time. Walls, ground and roads are cool greys; walkable towers are light blue; the sun keeps its real colour.
The city and the room stay the brightest things on screen, so the interface is tuned around them.
Three systems in two weeks
Warm Stone ran from 28 October to 4 November 2026, then Ink and Stone, with one Amber accent, until 11 November. Both read as luxury real-estate gold. The Apple-like system that replaced them uses cool neutrals and one blue, so the homes and the city carry the warmth instead of the interface.
