Re: Web Bluetooth | Specification Status and way forward

> At the moment we are worried that the specification is still very much in
flux. Is there a timeline for when the specification will be
final/recommended?

The parts of the specification which are not marked "unstable" are
implemented in Chromium and available in most Chromium-based browsers, such
as Google Chrome and Microsoft Edge, as stable and supported features.
There are many additional features which could be added to the API, so it
is unlikely a complete "final" version will be available for some time (if
ever). Specification work these days tends to favor the "living standard"
approach in which the specification evolves over time, but maintains
compatibility with existing code.

>  Is there any movement in terms of "implementation in Safari"?

The WebKit project continues to be opposed to generic peripheral access
APIs such as Web Bluetooth. This is unfortunate given that WebKit is the
only engine allowed on iOS devices. There are however some purpose-built
iOS browsers which have added implementations of Web Bluetooth on top of
WebKit to be found in the App Store, but it has not been added to a major
browser on iOS.

Reilly Grant | Software Engineer | reillyg@google.com | Google Chrome
<https://www.google.com/chrome>


On Fri, Sep 13, 2024 at 1:02 AM Stefan Bartnick <stefan_bartnick@web.de>
wrote:

> Hello web-bluetooth-group,
>
> we love what you do and follow the activity around the Bluetooth topic
> with great interest. We would like to use the standard in the browser
> (chrome) to some devices of our network.
>
> At the moment we are worried that the specification is still very much in
> flux. Is there a timeline for when the specification will be
> final/recommended? Is there any movement in terms of "implementation in
> Safari"? Information on both points would be great and would help us with
> the timing or go/no-go decision for implementation.
>
> BR
>
> Stefan
>