From a 3D building to an apartment: designing a connected property journey

A prospective buyer explores the building, opens a floor plan, selects an apartment and inspects the interior. The scale changes at every step, while the underlying choice remains the same. When the visitor must repeatedly search for the unit number and reconcile different labels, the website makes them assemble the journey themselves.

The demonstration connects these steps. A visitor can rotate the building, choose a floor and layout, then enter the apartment in 3D. This makes the full product journey visible. Its usefulness depends on how well information and choices survive the transitions.

The opening view presents the building, courtyard and surrounding area, with day and evening modes. Selecting a floor opens a plan containing the example apartments. The visitor can then enter an interior, change finishes and furniture, inspect the 2D plan and take a first-person walkthrough.

This is a working demonstration rather than the live inventory of a real development. Architecture, availability and prices are illustrative, and any sales effect remains a hypothesis. Within that boundary, the example shows which context needs to travel between screens: the development, floor, apartment, layout and selected options.

An operational version needs an agreed source for each property’s information. Unit number, floor area, availability and layout should not be independent labels maintained separately in several parts of the website. When a sales representative changes availability in the working system, the website needs a consistent update. Otherwise, an impressive visual journey could end in a conversation about an unavailable unit.

Saved configurations also require a policy for catalogue changes. A finish might be discontinued, a furniture model replaced or an estimate revised. The returning visitor needs a clear outcome: the original selection, identified changes or a request to choose an alternative. Establishing this behaviour early is more manageable than fixing it after a large catalogue has been created.

A buyer may inspect an interior, return to the floor and compare a neighbouring apartment. Preserving the chosen property and options, providing an obvious return path and supporting a link to the specific selection all help that process. A link to the home page does not communicate the work already done.

Ordinary viewing conditions deserve attention too. On a phone, the floor plan must allow a unit to be selected confidently. While an interior loads, the visitor should know which apartment is opening. If the 3D view cannot run, the core property information and a route to contact should remain available.

An enquiry completes the journey. Alongside contact details, the sales team can receive the unit identifier, configuration and the buyer’s actual question.

Give early participants a concrete task: find a suitable floor, compare two units, inspect one and send a question. This reveals unnecessary backtracking, lost selections and unclear labels. The number of 3D launches alone cannot explain where a visitor struggled.

After release, examine progression between steps and the enquiries they produce. Does an enquiry identify a particular unit? Can a representative continue the conversation without asking the buyer to reconstruct their choices? Interpret those observations alongside traffic sources, available stock and the sales process so that unrelated changes are not attributed to the interface.

The updating workflow matters as well. If every availability change requires several manual edits, a growing catalogue will increase operating effort even when the front-end experience looks polished.

A first release can focus on one building, a representative floor and several contrasting layouts. Carrying a selected apartment through a complete journey is more useful for evaluation than presenting a large catalogue with broken transitions. Expansion can then reuse the data rules and interaction patterns already tested.

The Russian-language video demonstrates the journey from the building to an apartment and its configuration. To discuss a similar project, a useful starting point is the current inventory, its source of availability data and the information a sales representative needs from an enquiry.