Re: [w3c/gamepad] Vibrate feature for Gamepad (#19)

This feels pretty good to me! A few thoughts:
- The naming doesn't matter to me too much, but maybe "vibrate" meshes better with existing interfaces than "rumble"? ("Haptics" feels like a great name, though!)
- Keeping with the existing vibration API, it would be nice if the duration accepted both a single duration and an array to use as a pattern.
- Assuming that intensity is a normalized 0-1 float? Should also specify that it may be snapped, so that devices with only a single intensity (Vive controllers) treat 0.8 as 1.0 (not sure if it should be rounded or simply non-zero in that case.)
- For devices like the Xbox pad where the motors are different frequencies I've heard requests that  we somehow indicate the type of motor being interacted with. It's an interesting idea, but I don't have a clue how to meaningfully expose such a thing. If you have thoughts on it would be interesting to discuss, but I think it's probably just not realistic.

---
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/issues/19#issuecomment-237632496