What a Web 3D Experience Should Show

A web based 3D experience is used by somebody alone. No agent, no introduction, no context, and no patience.

That single condition should determine every content decision, and it usually does not, because these experiences are frequently designed by people who have only ever seen them demonstrated by somebody who built them.

The visitor you are actually designing for

They arrived from a link, on a phone, in the evening, possibly while watching something else.

They have not decided they are interested. They are deciding whether to become interested, and that decision takes seconds rather than minutes.

They will not read instructions, will not watch an introduction, and will not wait for a loading bar to finish out of politeness.

Designing for that person produces a very different result from designing for somebody sitting in a sales gallery beside an agent.

The first screen has one job

It has to establish what this is and where, immediately and without interaction.

A recognisable view of the building in its setting does that. An abstract animation, a logo sequence or a slow camera move does not, because the visitor spends the only seconds they have working out what they are looking at.

The temptation to open with atmosphere is strong and it is a mistake in this format specifically, because atmosphere requires attention that has not been earned yet.

Then it has to say what it can do

An experience with no visible affordances gets treated as an image and abandoned.

Something has to indicate, within a moment, that this can be turned, entered, or explored. A subtle drift, a visible control, a hint on the first touch.

The failure to avoid is a beautiful static first frame that a visitor screenshots and leaves, never discovering that it was interactive at all.

The order of questions when nobody is guiding

In a gallery an agent shapes the order. Here the visitor does, so the structure has to match how they naturally ask.

What does it look like. Where is it. What is around it. What can I get. What does that one look like inside. What does it cost. What happens next.

That sequence is remarkably stable across projects, and an experience that supports it in that order feels intuitive while one that imposes a different order feels like work.

Exterior before interior, always

The building in its setting establishes the frame everything else hangs on, and skipping it leaves a visitor looking at rooms with no idea where they are.

This is more important online than in a gallery, because in a gallery somebody explains the context verbally and here nobody does.

It also matters for credibility. An experience that shows the real surroundings, including the unflattering parts, earns trust that a floating building on a white background cannot.

Plans have to be readable, not decorative

Every visitor reaches the plans and most experiences treat them as an afterthought.

A plan that is legible on a phone, with dimensions in terms somebody can use and furniture that indicates scale, answers the question people actually have, which is whether their life fits in it.

An architectural sheet reproduced at phone size answers nothing and is the point where a meaningful share of sessions end.

Views have to correspond to something real

The view is frequently the reason a unit is worth more, and it is the claim most easily made loosely.

A view labelled as being from a specific unit should be from that unit, at that height, looking where a person would look. Anything else is a representation that will be checked later, when it is much more expensive to have been wrong.

Where views are indicative rather than specific, saying so plainly costs very little and protects a great deal.

Price and availability, or a clear absence of them

An experience that shows neither leaves the visitor with the one question it cannot answer, and they go looking elsewhere.

An experience that shows both takes on an obligation to keep them current, and a stale figure damages more than a missing one.

The workable middle is a range, clearly framed as indicative, with a route to a current answer. That satisfies the question without creating a maintenance liability nobody will honour.

Something has to happen at the end

A session that simply stops leaves the visitor at a dead end with whatever interest they had, and no route to act on it.

A clear next step, a way to be contacted, a way to save or send what they looked at. None of it aggressive, because aggression at that moment loses people who were nearly convinced.

The most valuable of those is sending. A visitor who forwards it to somebody else has just done the marketing that a brochure never does.

What to leave out

The vision film. Nobody watches a film they did not choose to start, and the seconds it consumes are the ones that decide the session.

Audio. It plays in a public place or with the volume off, and either way it is a liability rather than an asset.

Anything requiring an account before seeing anything, which converts a browsing visitor into a bounced one.

Guided tours with no exit, because the visitor came to look at what interests them, not what interests the developer.

Navigation people actually understand

Free camera control sounds generous and produces disorientation, because most visitors have no practice moving a camera in 3D space.

Constrained navigation with a few good positions is more usable than unlimited freedom, and it also happens to protect the project from being viewed from angles that were never designed to be seen.

The compromise that works is a small set of designed viewpoints, with limited freedom around each, and a reliable way back to a known position.

Designing for the second visit

People return to these experiences, frequently with somebody else, and the return visit has different needs from the first.

The first visit is orientation. The second is comparison, usually of two specific units, and an experience that makes somebody navigate the whole thing again to reach them wastes the visit.

A way to return directly to a specific unit, by link, is a small feature with a disproportionate effect on how the decision progresses.

The phone is the primary device, not the fallback

Property research happens on phones, and web 3D experiences are frequently designed on desktops and adapted downward.

Designing for the phone first changes real decisions: how large controls are, how much text fits, how many things can be on screen, and how much detail survives at that size.

An experience that is excellent on a laptop and cramped on a phone has optimised for the minority of its audience.

Honesty about what is not built yet

Everything shown is a proposal, and the experience should be able to say which parts are settled and which are not.

Landscape that has not been designed, amenity spaces still in progress, facade materials being priced. Showing them as finished is how a buyer ends up feeling misled by a change nobody intended to hide.

Labelling by status is a small production overhead and a large credibility asset, and it is also the record that matters if a change is ever disputed.

Accessibility, which improves it for everybody

Legible type, adequate contrast, generous touch targets, and an experience that works without sound are accessibility measures and also simply better design for a phone in daylight.

The specific requirement worth insisting on is that nothing essential is communicated only by colour or only by audio.

It costs nothing when specified at the start and it is expensive to retrofit after the build.

What the analytics should be designed to answer

This format reports on itself, and deciding what to measure before building is what makes the data useful.

Which unit types were opened, how long people stayed with each, which views were revisited, and where sessions ended.

Those answer commercial questions. Which plan is ignored, whether people leave at the price, whether one aspect is being explored disproportionately, which is a pricing signal before it is a marketing one.

Added afterwards, tracking measures whatever was convenient. Designed in, it measures what somebody actually needs to know.

Loading is part of the content design, not a technical afterthought

The loading moment is the first thing every visitor experiences and the only part of the experience that is guaranteed to be seen by everybody, which makes it strange that it is almost never designed.

What appears during it matters. A blank screen with a spinning indicator communicates nothing and gives the visitor no reason to stay. A recognisable still of the building, or the name of the development with a line about what it is, gives them something to hold while the rest arrives.

Better still is showing something real quickly and improving it. A simplified building that appears in two seconds and sharpens over the next five keeps somebody who would have left, because the wait now has a subject.

Treating loading as content rather than as a delay changes who is still present when the experience is ready, and that is the number every other design decision is competing for.

The gap between a demo and a deployment

Almost every web 3D experience that disappoints was signed off in a meeting where somebody who built it was driving, on a laptop, on office wifi, with the room paying attention.

None of those conditions exist in deployment. The visitor drives it themselves, on a phone, on a connection nobody controls, while distracted, with no explanation available and no reason to persist.

The design decisions that survive that transition are the ones made with it in mind. Larger controls than look necessary. Fewer things on screen than the designer wants. Text sized for a hand rather than a desk.

The single most useful discipline is to review the experience only on a phone, held at arm length, in a room with a window. Anything that fails that review will fail in deployment, whatever it looked like in the meeting.

Content the visitor came for versus content the developer wants shown

These two lists overlap less than most project teams expect, and where they conflict the visitor list should win.

The developer list tends to lead with the vision, the design intent, the architect, the sustainability credentials and the amenity programme. All legitimate, all appropriate somewhere, and none of them the reason somebody opened a link at nine in the evening.

The visitor list is smaller and more practical. What it looks like, where it is, what is available, what it costs, and whether their life fits inside it.

An experience that answers the visitor list first earns the attention to deliver the developer list afterwards. One that opens with the developer list frequently never gets to the rest, because the session ended.

Testing it the way it will be used

Give the link to somebody who has never seen the project, on their own phone, and say nothing at all.

Watch what they do in the first ten seconds, and whether they discover that it is interactive.

Ask afterwards what they remember and what they still do not know. The gap between those two is the content that is missing.

This test costs nothing, takes ten minutes, and catches more than any internal review, because internal reviewers already know what the thing is.

A configuration that works for most developments

A recognisable exterior in its real setting that appears within a few seconds.

A simple way into the plan list, with plans legible at phone size.

Real views from real positions for the units that differ meaningfully.

An honest indication of price and status, with a route to a current answer.

A way to send it to somebody else, and a clear next step.

Nothing else. Everything beyond that list should have to justify the weight it adds, because weight is the audience it removes.

Frequently asked questions

What should the first screen show?

A recognisable view of the building in its setting, appearing without interaction. Abstract openings and logo sequences consume the few seconds that decide the session, because the visitor spends them working out what they are looking at.

How do we stop people thinking it is just an image?

Something has to indicate interactivity within a moment: a subtle drift, a visible control, or a hint on first touch. A beautiful static first frame gets screenshotted and abandoned by visitors who never learn it could be explored.

Should the experience show pricing?

Showing nothing leaves the question it cannot answer and sends people elsewhere. Showing exact figures creates a maintenance obligation that stale data will break. An indicative range with a route to a current answer usually satisfies both.

Is free camera control a good idea?

Rarely. Most visitors have no practice moving a camera in 3D and free control produces disorientation. A small set of designed viewpoints with limited freedom around each, and a reliable way back, is more usable and protects unplanned angles.

How should we test it?

Hand the link to somebody who has never seen the project, on their own phone, and say nothing. Watch the first ten seconds, then ask what they remember and what they still do not know. The gap is the missing content.