Permalink
Switch branches/tags
Nothing to show
Find file Copy path
105 lines (84 sloc) 7.53 KB

Implementation Status

This document shows the implementation status of Web Bluetooth on the different browsers.

Chrome browser logoSamsung Internet browser logoOpera browser logoServo browser logoFirefox browser logoMicrosoft Edge browser logoSafari browser logo

Chrome

Work is in progress:

  • Know How to file Web Bluetooth Bugs.
  • In Chrome OS, Android, & Mac, the GATT Communication API is shipped without any flag.
  • Linux & Windows are partially implemented, but not supported. The chrome://flags/#enable-experimental-web-platform-features flag must be enabled.
  • New Windows implementation is available by running Chrome with --enable-features=NewBLEWinImplementation.
  • Root Issue 419413: Web Bluetooth and blocking issues are most authorative on status.
  • Some Bluetooth GATT operations can't be run in parallel yet. See #188 (comment)

GATT Communication API

Feature/Platform Chrome OS Android Mac Linux Windows
getAvailability()
Referring Device (Physical Web)
Discovery
└ Service list
└ Name or prefix
└ Manufacturer/Service data
└ acceptAllDevices
Chooser UI
permissions.request()
permissions.query()
permissions.revoke()
watchAdvertisements()
Persistent Device IDs
GATT Server Connect
GATT Server Disconnect
Hanging connect() abortable by disconnect()
getPrimaryService*()
getIncludedService*()
getCharacteristic*()
Characteristic Properties
Read Characteristic
Write Characteristic
Start/Stop Notifications
Descriptors
Event bubbling
Device Disconnected Event
Service Changed Event
BluetoothUUID
TypeError for bad UUIDs
Invalidate GATT attributes upon disconnect
GATT Blocklist
Low-latency Blocklist Updates

Scanning API

Feature/Platform Chrome OS Android Mac Linux Windows
Advertisements Scanning

Tip: Chrome channel releases are tracked at https://googlechromelabs.github.io/current-versions/.

Notes

  • Android: Requires Android 6.0 Marshmallow or later.
  • Mac: Requires OS X Yosemite or later.
    • Some MacBooks may not work: Check "About this Mac" / "System Report" / "Bluetooth" and verify that Low Energy is supported.
  • Linux: Requires Kernel 3.19+ and BlueZ 5.41+ installed. Read How to get Chrome Web Bluetooth working on Linux.
    • Note that Bluetooth daemon needs to run with experimental interfaces if BlueZ version is lower than 5.43: sudo /usr/sbin/bluetoothd -E
  • Windows: Requires Windows 8.1 or later.
    • To discover devices the user hasn't yet manually paired, requires Windows 10.
    • A third-party Windows 10 Polyfill (Chrome Extension + Native Executable) has been created while Windows support is not implemented yet.

Unsupported platforms

  • Android WebView: Will be supported in the future.
  • iOS: Uses the web exposed APIs as provided by the WKWebView, no implementation planned in the Chromium codebase.

Note: WebBLE is an app for iOS that supports the GATT Communication API. It was created initially for the Puck.js project.

Samsung Internet

In Samsung Internet v6.4, the GATT Communication API is shipped without any flag.

Opera

Available behind a flag opera://flags/#enable-web-bluetooth.

Servo

https://szeged.github.io/servo/

Firefox

Microsoft Edge

https://dev.windows.com/en-us/microsoft-edge/platform/status/webbluetooth

Safari

https://bugs.webkit.org/show_bug.cgi?id=101034

Node.js

Node.js ports are available: