- From: Anssi Kostiainen <notifications@github.com>
- Date: Mon, 23 Feb 2026 21:32:39 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/1187/3949198853@github.com>
anssiko left a comment (w3ctag/design-reviews#1187) To address the concerns, the group has delivered the following: As for the Generic Sensor API & Accelerometer, Gyroscope, and Orientation Sensor, the group has published an [explainer document](https://w3c.github.io/motion-sensors/), a [use cases document](https://w3c.github.io/sensors/usecases), and [demos](https://w3c.github.io/generic-sensor-demos/) that address the user needs and use cases concerns for these deliverables. Furthermore, Rick Waldon, an industry-recognised sensor tech expert, and a W3C Invited Expert, has explained the benefits of the Generic Sensor API architecture in [this article](https://bocoup.com/work/generic-sensor-api-for-the-web-platform). As for the Vibration API, the group’s plan of record is to use the Security IG's newly published [threat modeling guide](https://www.w3.org/TR/threat-modeling-guide/) as a framework to understand the privacy and security concerns, and appropriate mitigations. As for the Battery Status API, the group has produced an [explainer for a higher-level battery signal](https://github.com/w3c/battery/blob/gh-pages/energy-saver-mode-explainer.md) and continues to discuss new API shapes and use cases for this feature. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1187#issuecomment-3949198853 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1187/3949198853@github.com>
Received on Tuesday, 24 February 2026 05:32:43 UTC