- From: Kenneth Rohde Christiansen via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Mar 2017 14:55:14 +0000
- To: public-device-apis-log@w3.org
>From a user point of view (user being front end dev or the like) - they will mostly care about the actual orientation values and know that the latency will be different between something connected and something external, but it is not like that they will drop using a headset because of latency issues, if what they care about is the headset orientation :-) It is all about balance. If we say that these are super low level APIs and that libs need to be built around them to make the APIs consumable, well then we can very well get away with only having populate methods and nothing for the simple case, which you were arguing for :-) But then again, I don't think having a low levelish API means it is mutual exclusive that the API can be nice and that something has to be build around it. -- GitHub Notification of comment by kenchris Please view or discuss this issue at https://github.com/w3c/sensors/issues/170#issuecomment-283974440 using your GitHub account
Received on Friday, 3 March 2017 14:55:21 UTC