Re: [w3c/gamepad] Added a supplemental "Extensions" spec (#32)

Regarding devices like Leap Motion and Perception Neuron: I don't believe that these are good fits for the Gamepad API. Other VR input devices like Oculus Touch, The Vive wands, and the Daydream controller all resemble a more traditional game controller with motion tracking capabilities. They have buttons and axes, etc. Something like Leap Motion has effectively zero mapping to the base Gamepad API and only a tenuous mapping to these extensions. As such I don't think it's wise to target them with this API.

That being said the Leap Motion does have a pretty nice Javascript API that's driven by WebSockets. It allows the API to be very targeted and expressive, and I haven't found it to be terribly latent. It's installed with their runtime, so it's available on any PC which has their drivers. I've found that to be a very effective model for exposing that sort of hardware, and if we get to a point where that level of hand tracking is normalized and looking for a standardized web API I think we would do well to take notes from their existing work in that space..

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/pull/32#issuecomment-246865740