You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although I see a lot of improvement over earlier scattered sensor APIs, I would strongly suggest that the API will also embrace sensors dynamically added/removed.
A use case that might very well happen soon:
I am sitting in my house looking at a temperature widget. The web app widget is connected to both my phone temperature sensor and a temperature sensor outside my kitchen window.
I walk out to my car, losing connection with the sensor in my house - but keeping connection with the phone's sensor.
I start my car and my web app widget discovers the inside and outside temperature sensors in the car and shows them in the widget
now... there are a few issues with the current API for this to happen:
to have a new TemperatureSensor() in the first place, the browser needs to know about a 'TemperatureSensor' or it needs to be added with some polyfill (= not very generic)
I don't see any mechanism/events for adding/removing sensors
I see only a short example of a very specific way of addressing multiple sensors in the tire pressure example ... IMO, we need sensor discovery based on physical properties (e.g. tire pressure sensors can (also) be found by searching for sensors related to 'rotating motion' & 'air pressure' ... )
The text was updated successfully, but these errors were encountered:
Although I see a lot of improvement over earlier scattered sensor APIs, I would strongly suggest that the API will also embrace sensors dynamically added/removed.
A use case that might very well happen soon:
now... there are a few issues with the current API for this to happen:
The text was updated successfully, but these errors were encountered: