Skip to content

In The News

Live
Devmeta-oakley-hstn-sandbox — Sandbox for trying Android, iOS, Unity, and Flutter builds on Oakley Meta HSTN glasses.DevDeez-Spacesaver-PC — Guided Windows disk cleanup — scan, recommend, and clean safelyDevDeez-Fuel-Gauge — Lightweight Windows/Mac desktop overlay showing Cursor, Claude, Codex usage cap + Harddrive, CPU, GPU & RAM monitoringDevDeez-Currency-Calculator — Deac's Currency Converter — fiat/crypto PWAWritingThe Best Local AI Models to Run Offline, November 2026WritingWhat hands-first input means for Meta Quest projectsWritingHow to guide attention in 360 video without arrowsWritingWhy 8K 360 video still looks soft in a headsetWritingHow to prototype an audio-first smart glasses experienceNowGlass Angels, our VR piece set in the Owl House in Nieu-Bethesda, was on the Fak'ugesi 2026 exhibition floor. Mosaic owl headset and all.DistributionVenice Immersive — In Competition 2024 — StrangewaysDistributionVenice Immersive — In Competition 2021 — Spirit of Place · BlissDistributionVenice Best of Worlds — 2024 — Mormoverse, Under The PillowDistributionEmmy Awards — VRChat previews — Reeducated, ISS ExperienceDistributionWebby Awards — People's Voice 2023 — Oxymore, Jean-Michel JarreDistributionSpirit of Raindance — BloodbathDistributionSpirit of Raindance — MyceliaDistributionLoeries — Silver & Bronze — Life of Confidence, Made In The CapeDistributionSmarties — Silver — FVRM for AbsaDistributionMona — Design Prize — Renaissance of the Metaverse 2022DistributionThe Cradle of Humankind (2025–Present) — iOS & Android · UNESCO siteDistributionStrangeways: The Only Way Out Is Through (2026) — Live VR theatre · ran 9–11 Oct 2026DistributionVenice Immersive Worlds Gallery (2024–2026) — Official venue · 3 editions · 145,000+ VRChat visitsDistributionMade in the Cape Market (2023) — Gold IAB Bookmark · 3× Bronze Loeries
← Back to writing

What hands-first input means for Meta Quest projects

Design the task, not a replacement gesture for every Quest button.

What's the problem?

Meta’s direction needs one important clarification. Current Quest headsets support controllers and hand tracking. Meta VR Glasses, planned for spring 2027, make eyes and hands the default, with controllers sold separately.

That change still affects Quest projects now. Both product lines use Meta Horizon OS, while existing Quest titles provide the starting point for many future ports.

Controllers hide several useful assumptions. They provide triggers, thumbsticks, labelled buttons and haptic feedback, meaning physical vibrations. They also support several inputs at once. A player can move, turn and grab simultaneously.

Hands offer fewer reliable inputs. They cannot vibrate when an action succeeds. They may disappear when cameras lose sight of them. Occlusion, where one hand blocks the camera’s view of another, can interrupt tracking.

The common mistake is mapping each button to a new gesture. Meta’s guidance from 12 November 2026 warns against this approach. Similar gestures become difficult for software to distinguish and difficult for people to remember. Quest’s four controller face buttons have no standard hand equivalent.

Onboarding assumptions also break. “Press A to continue” is precise. “Make this unfamiliar pose” needs a demonstration, feedback and room to practise. Testing with experienced team members will rarely reveal that confusion. They already know what the system expects. Convenient, but useless.

What's the solution?

Start by listing actions rather than controller inputs. Write down what the person must accomplish: select, grab, rotate, place, confirm, move or open a menu.

Then simplify the critical path, meaning the shortest sequence needed to complete the main task.

Imagine a Quest training experience where someone picks up a virtual component, rotates it, places it and presses A to confirm. A hands-first version could use a natural grab, direct wrist rotation and a placement zone that confirms automatically when alignment is correct.

We have removed the final button instead of inventing a confirmation gesture.

Keep the primary action direct. Use established interactions such as index-finger touch, palm grab and pinch selection. A microgesture, which is a small finger movement such as a thumb tap, can handle navigation where direct manipulation does not fit.

Make targets more forgiving. Increase button sizes and extend colliders, the invisible regions that detect contact, slightly beyond visible objects. Add clear colour, sound or motion feedback because hands provide no haptic confirmation.

Plan what happens when tracking fails. A held object might pause in place, return safely or remain attached briefly. Never let it vanish or complete an irreversible action without warning.

Teach one repeated action first, beside the object where it happens. Show the recognised gesture and let people practise without penalties. If your project supports controllers too, change instructions when the input changes and preserve progress during the handover.

Testing now needs several layers. Use Meta XR Simulator for early interaction work. Test supported hand interactions on Quest hardware. Recruit people who have not seen the prototype. Finally, test on the intended hardware because simulation cannot reproduce physical tracking, lighting or field-of-view limits.

Keep controllers where precision, rapid timing, haptics or movement outside camera view remain essential. Hands are a design option, not a compulsory conversion.

What's next?

  1. Audit one core Quest flow and replace button names with user actions.
  2. Prototype its most repeated action using only touch, grab or pinch.
  3. Test it with three new users, including tracking loss and input switching.

Share what you redesign, or ask a question about a stubborn controller interaction.

Virtually yours, Deac

— The worldbuild.io infoBot