The Honest Caveats

Start with the physical reality of the devices, because it is the caveat people forget between demos. A headset capable of the immersion this module has praised is, today, a substantial object strapped to your face. It has weight, concentrated at the front, that becomes a strain on the neck over time. It generates heat and traps it against your skin. It seals you off, so the real world - your desk, your colleagues, your cup of tea - vanishes. And it is tiring in a way an ordinary screen is not: the concentration, the slight unnaturalness of the optics, the physical burden all add up, so that comfortable, unremarkable, all-day wear does not yet exist anywhere, at any price. This is not a detail that the next model will quietly fix; it is the current state of the art, and honesty about it is essential.

The consequence for practice is concrete. Spatial computing is well suited to sessions - a focused design review, a client walkthrough, a coordination check - measured in minutes, not to being your working environment for hours. Anyone promising that you will soon spend your design day inside a headset is selling a future the hardware has repeatedly failed to deliver. The heavy, hot, isolating, tiring nature of the devices is a first-order design constraint on how and when you use them, not a footnote. It means immersion is something you enter deliberately, for a bounded purpose, and then leave - which is a perfectly good way to use a powerful specialised tool, as long as nobody pretends otherwise.

There is also a plain reliability and friction dimension. Devices need charging, updating, setting up, and a clear physical space to use safely; tracking can drift; a session that should take two minutes to start can take twenty when something needs an update. None of this is fatal, but all of it is real, and it is invisible in the polished demo that sells the technology. The honest framing is neither dismissal nor hype: the hardware is genuinely capable of remarkable things in short bursts, and genuinely not ready to be a comfortable, always-on part of the working day. Treat any specific device as a fast-moving, illustrative example rather than a settled solution, and lean on the manufacturers' own guidance for how long it is meant to be worn and how to use it safely - the health and comfort of the person in the headset is their domain, not a matter of guesswork.

The second caveat is economic, and it has two parts that the excitement tends to hide. The first is the obvious cost of entry: capable headsets, and where needed the powerful computers to drive them, are real money, and in Indian terms a high-end 'spatial computer' plus its supporting hardware is a serious outlay for a small practice. This is softening - affordable standalone headsets and tablet AR bring the entry price down sharply - but it never falls to zero, and the temptation to buy the most impressive device rather than the one the task needs makes it worse. The honest advice is to spend on the least capable setup that does the specific job you have identified, not on the future you are imagining.

The second, less visible cost is preparation effort, and it is often the bigger one. A design model does not drop into a headset ready to walk through. It has to be prepared: geometry optimised so it runs smoothly, materials and lighting set up, the scene organised, the experience tested. For a real-time immersive walkthrough this can be hours of skilled work per review, and it is work that produces nothing you can put in a drawing set - it exists only to enable the session. That is a genuine tax on every immersive use, and it is completely absent from the demo, where someone else prepared the scene in advance. A busy practice with deadlines has to weigh that preparation time against the value of the session honestly, because it is time not spent on the drawings, details and documents that the project actually requires.

Together these mean spatial computing carries both a cost of entry and a cost per use, and both compete directly with alternatives that have almost none. A drawing costs nothing extra to produce beyond the design work you were doing anyway, and a screen review needs no special preparation at all. So the immersive session has to deliver enough value to justify not just the device but the hours of setup it demands - which is a high bar for routine tasks and an easy one only for the handful of moments where true-scale understanding or client buy-in genuinely changes the outcome. This is the arithmetic behind 'earn its place': not hostility to the technology, but a sober accounting of what each use actually costs against what it actually returns.

The third caveat is about the human body's response, and it is not a marginal problem. A meaningful fraction of people experience VR sickness - a form of motion sickness with nausea, disorientation, sweating or headache - when they are in an immersive experience, especially one involving artificial movement through space. The leading explanation is a sensory conflict: your eyes report that you are moving while your inner ear reports that you are sitting still, and the mismatch makes some people unwell, sometimes quickly. Susceptibility varies widely between individuals and is hard to predict, which matters enormously when the person you have put in the headset is a client whose comfort and confidence you cannot afford to lose. A queasy client is not a persuaded client.

There are related comfort issues even for people who do not feel sick. Current optics create a vergence-accommodation conflict - your eyes converge on a virtual object at one apparent distance while focusing on a screen at a fixed physical distance, an unnatural combination that contributes to eye strain and fatigue over time. Add the weight, heat and isolation from the first caveat, and the result is that immersive sessions are inherently tiring and best kept short. Good practice - smooth, comfortable movement schemes, keeping sessions brief, seating people, having a way out - reduces the problem, and the manufacturers publish comfort and safety guidance that should be followed, but none of it eliminates individual susceptibility. This is a genuine constraint on who you can put in a headset and for how long.

There is also an accessibility dimension that honesty requires naming. Headsets are not usable comfortably or safely by everyone: they interact awkwardly with some vision conditions and spectacles, can be unsuitable for people with certain balance, neurological or health conditions, and assume a physical space and a degree of mobility not everyone has. A tool that a portion of your clients or colleagues cannot use, or cannot use without discomfort, has a real limit on its universality that a drawing - which anyone can look at - does not. The honest stance is to treat comfort, sickness and accessibility as first-class constraints, defer to the manufacturers' guidance and to medical advice where health is involved, always keep a non-immersive alternative available so no one is excluded from understanding the design, and never treat a person's discomfort as a minor inconvenience to push through for the sake of the demo.

The final and most important caveat is the one that ties the module together: for a large share of everyday design work, a screen or a drawing is not a compromise but genuinely the better tool, and pretending otherwise is the core mistake the whole course is written against. Think about what most design hours actually contain. Precise drawing and editing - moving a wall, adjusting a dimension, detailing a junction - is faster and more exact with a mouse on a screen than with any spatial input. Documentation, annotation and the production of a coordinated, legible, contractual set of drawings is a task drawings were invented for and do incomparably. Sharing information - sending a plan to a consultant, a contractor, an approving authority - is instant and universal with a drawing and awkward or impossible with an immersive model. Quick checks, comparisons and back-and-forth iteration are all faster on a screen.

Against that, the immersive session is heavy, costly, tiring, prep-hungry and shareable only with people who are also 'in'. So on the everyday tasks the screen and drawing win decisively, and the honest designer reaches for immersion only where its specific strengths - true-scale understanding, embodied spatial judgement, presence for client communication and buy-in, on-site overlay - genuinely change the outcome. That is a real but short list, and recognising it is the skill. Immersion must earn its place, task by task. The test is simple: does this particular task need the body inside the space at true scale, or need a non-designer to understand a space they cannot read? If yes, and the value is worth the cost and the preparation, reach for the headset. If not - and usually it is not - the screen or the drawing is not second-best; it is the right tool.

This is why the competent stance is neither the evangelist's nor the cynic's. The evangelist wastes effort and goodwill forcing immersion onto tasks a screen does better, and eventually the technology gets blamed for the mismatch. The cynic misses the handful of moments where immersion is genuinely transformative and no drawing will do. The disciplined designer holds both truths - the real power and the real cost - and routes each task accordingly, always remembering the boundary that runs through everything: even when immersion earns its place, it is a tool for seeing and communicating, never a source of truth, so binding dimensions, technical decisions, setting-out and compliance stay with the verified BIM and drawings, qualified engineers, licensed surveyors and the governing codes, including the National Building Code of India. Earn its place, and keep it in its place.