Imagine you’re inside a virtual room. You want to get rid of a chair. Your instincts scream: find a menu, a trash icon, a delete button. But there’s nothing. Instead, you reach up and long-press the ceiling. The chair vanishes.
Welcome to the future of spatial computing – where the interface is the architecture, and your gestures are anything but intuitive. This is the world of voxel and depth-pixel rendering, a technique that bypasses traditional polygon bottlenecks by treating the digital world as a grid of discrete volumetric data. It’s fast. It’s efficient. And it forces you to interact with the room itself, not a floating menu.
Polygons gave us menus. Voxels give us walls.
You’ve probably noticed that most AR/VR experiences still feel like 2D screens glued to a 3D space. Buttons, sliders, text panels – all the familiar crutches. The problem is that polygons are expensive to render in real-time. Voxels? Cheap. But they come with a catch: you can’t just click on a virtual button. You have to long-press a surface to pick something up, long-press the floor to place it, long-press the ceiling to create a wall. The user comment on the original article says it all: ‘Long press on the ceiling to create walls.’ That’s not a bug. That’s a feature.
Here’s where the tension hits: the very technique that makes spatial computing fast also makes it clunky. You want god-like control over your digital environment? Great. But you’ll have to learn the physical grammar of your own space. The ceiling becomes a delete key. The floor becomes a placement zone. The walls become your toolbar.
The most intuitive interface is the one you don’t see – because you’re too busy using the floor.
We’ve been conditioned to believe that good UI is invisible. But here, the UI is the whole room. And that’s a radical shift. The future of spatial computing interfaces isn’t on-screen menus or buttons – it’s architectural surfaces themselves. Floors, ceilings, and objects acting as the primary functional UI. This is brilliant. Not because it’s easy, but because it’s honest. True spatial computing doesn’t fake a 2D menu in 3D space. It turns your physical environment into a functional controller.
If your spatial UI still uses buttons, you’re building a 2D world in 3D drag. Stop.
The next time you find yourself long-pressing a ceiling, remember: you’re not fighting the interface. You’re learning the language of the new reality. Speed demands sacrifice. And the sacrifice of a few awkward gestures is a small price for the power to reshape your world with a single touch.
FAQ
Q: This sounds like a gimmick. Why would anyone design a system with such awkward gestures?
A: Because speed demands sacrifice. Voxel rendering is computationally cheap, but it treats the world as a discrete grid. Your gestures become the only way to interact with that grid. It's not a gimmick – it's the necessary trade-off for real-time, high-fidelity spatial computing. The awkwardness is a feature, not a bug.
Q: What does this mean for developers building spatial apps?
A: Stop designing 2D menus floating in 3D space. Start thinking about how floor, ceiling, and wall surfaces can become functional zones. Long-press, swipe, tap on architectural elements. The physical environment is your canvas. Your app should map actions to surfaces, not to buttons.
Q: Isn't the whole point of good UX to make it intuitive? This seems like a step backward.
A: Intuitive is a moving target. The first computer mice were unintuitive. The key is consistency and discoverability. Once you learn that the ceiling is your delete button, it becomes second nature. The real contrarian take is that we've been too obsessed with 'natural' interfaces. True power comes from a deliberate, learnable gesture language – exactly what this system provides.