microgesture support
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17.6k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Description
The Quest Browser 38.1 support hand microgestures. They follow the OpenXR specification https://registry.khronos.org/OpenXR/specs/1.1/html/xrspec.html#XR_META_hand_tracking_microgestures and there is a demo page at https://micro-gestures-demo.glitch.me/ and the result show up in the GamePad API https://immersive-web.github.io/webxr-samples/controller-state.html
It could be interesting, assuming that others, e.g. Apple for the VisionPro or Google for AndroidXR do follow OpenXR specs for WebXR, to bring this to a similar level than hand-tracking-controls namely extending events beyond pinchstarted, pinchended and pinchmoved with, possibly (following OpenXR naming) tap (or maybe thumb_tap), thumb_location (that I initially forgot, as I somehow didn't manage to test it) and swipe_left, swipe_right, swipe_forward, and swipe_backward new events for example.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing hand-tracking-controls implementation, then compare its current events with the OpenXR hand-tracking microgestures specification and the linked demo and GamePad API sample. Done means agreeing on supported gesture names and behavior, extending the controls consistently, and covering the new events across the relevant browser implementations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- game-dev, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100