marcoscaceres
commented
9 months ago I think the problem with the API is exactly the one described by API itself, in that it's too simple:
- It doesn't actually provide means to be tactually expressive (just a single pattern, which might be confusing or meaningless);
- it's too susceptible to being abused as a notification mechanism - hence the concern about user annoyance.
- it doesn't provide any description of what "vibrate" actually means, thus would lead to different "feels" across devices, platforms, etc. (concerns around device independence and portability)
- And I guess it's subject to wasting significant power when used without care.
So it's not clear what the use case for this API is for or how it benefits users in a meaningful way.
MrBrain295
WebKittens
No response
Title of the spec
Vibration API (Second Edition)
URL to the spec
https://w3c.github.io/vibration/
URL to the spec's repository
https://github.com/w3c/vibration/
Issue Tracker URL
https://github.com/w3c/vibration/issues
Explainer URL
No response
TAG Design Review URL
No response
Mozilla standards-positions issue URL
https://github.com/mozilla/standards-positions/issues/907
WebKit Bugzilla URL
No response
Radar URL
No response
Description
In their words "The API is specifically designed to address use cases that require simple tactile feedback only. Use cases requiring more fine-grained control are out of scope for this specification. This API is not meant to be used as a generic notification mechanism. Such use cases may be handled using the Notifications API [NOTIFICATIONS] specification. In addition, determining whether vibration is enabled is out of scope for this specification."