Bluetooth is a standard for short-range wireless communication
between devices. This group is developing a specification
for Bluetooth APIs to allow websites to communicate with devices in a secure and privacy-preserving way. In particular the web Bluetooth API focuses on minimizing the device attack surface exposed to malicious websites, possibly by removing access to some existing Bluetooth features that are hard to implement securely. Further, the API takes the approach of a user interface to
select and approve access to devices as opposed to using certification
and installation.
Note: Community Groups are proposed and run by the community. Although W3C hosts these
conversations, the groups do not necessarily represent the views of the W3C Membership or staff.
Chairs, when logged in, may publish draft and final reports. Please see report requirements.
The Chrome team has announced a subset of the Web Bluetooth API is now enabled in Chrome on Android, Chrome OS, and Mac. The GATT Communication API enables users to select Bluetooth devices and pair them to a web site, e.g. to control a toy or interact with a retail kiosk. This enables greater convenience, and less security risk (via least privilege), than installation of a native application.
At the Chrome Developer Summit we announced the latest milestones in Web Bluetooth being available in Chrome for Android and Chrome OS. We also discussed the great match with the Physical Web project. Check out the video:
Participate using GitHub’s tools which enable following projects, filing issues (e.g. spec issues), submitting pull requests, etc. Email notifications make following along easy!
WebBluetoothCG/web-bluetooth
