Mikhail Pozdnyakov

We might not need to add discovery API per se at the moment, but simply having a "location" (or similar) parameter in SensorOptions would be beneficial.

tagging @andrey-logvinov

@andrey-logvinov thanks for your comments! I share your concerns regarding keeping CPU awake and etc. IMO it looks fine if an app is wake locking screen and CPU for a...

Why not just keep the existing semantics (`sensor.reading` property) and say that it always returns the same object instead of re-creating it every round? Mixing of sensor and it's data...

> Because it doesn't help us with requirements 2) and 3) above, makes for more verbose code (sensor.reading.x instead of sensor.x) As for 2) and 3) `sensor.reading.x ` is not...

We (me and @alexshalamov) have a concern that introducing of low(high)-resolution mode will be quite confusing for web developers who will not know exactly which permission token is required for...

So far it was [agreed](https://docs.google.com/document/d/1XThujZ2VJm0z0Gon1zbFkYhYo6K8nMxJjxNJ3wk9KHo) to proceed with the implementation without low/high precision modes. Moving this issue to level 2.

I would like to propose the following approach: ``` interface MotionSensor : Sensor { /** * Populates the passed array with the latest readings recorded right before the next *...

@tobie @anssiko PTAL

> We want to make sure the API design doesn't force the implementation to preemptively store all intermediary samples in case collectLatestReadings gets called in the following animation frame. I...