* W3C System Applications http://www.w3.org/wiki/System_Applications
* W3C System Application WG http://www.w3.org/2012/05/sysapps-wg-charter.html
* B2G WebBluetooth https://wiki.mozilla.org/WebAPI/WebBluetooth
* Chromium Bluetooth Extension API http://www.chromium.org/developers/design-documents/extensions/proposed-changes/apis-under-development/bluetooth-extension-api
Bluetooth Implementation on B2G https://bugzilla.mozilla.org/show_bug.cgi?id=727618
Are you going to work on adding this to WebKit? Please e-mail webkit-dev for discussion then.
I would personally strongly oppose to adding this feature to WebKit.
@Alexey, Web browsers must fallow the Web Standards and feature implementation time estimations.
As you can see Bluetooth API, Network Interface API, etc. has already LC, CR status http://www.w3.org/2012/09/sysapps-wg-charter.html
Discovery API must deliver also Bluetooth API access http://dev.webinos.org/specifications/draft/servicediscovery.html
> There is no reason to limit web applications to accessing services over WiFi, as there are many services that are either exposed directly by a device, or indirectly via USB, Firewire (IEEE 1394), Bluetooth or other interconnect technologies such as ZigBee (for sensors) and NFC. A proof of concept was developed in early 2011 as a browser plugin for mDNS, SSDP, SLP, USB and Bluetooth. This suggests that a W3C discovery and binding API should work with a range of interconnect technologies and discovery techniques.
Chrome Bluetooth API implementation:
From the W3C Web Bluetooth Community Group there is now a standard spec for this at https://webbluetoothcg.github.io/web-bluetooth/ and I believe it's already landed in Gecko in https://bugzilla.mozilla.org/show_bug.cgi?id=1005848 and also there's work in progress on a Blink implementation https://www.chromestatus.com/features/5264933985976320
Please consider seriously web-bluetooth API. This is a step forward in unleashing IOT power, and many companies (including mine, Logitech) are looking for it eagerly!
Would be pleased to participate.
Just to add my support for this as well. I develop Puck.js, and allowing web developers to control hardware in the real world straight from a webpage is going to lead to some amazing things being created.
Being able to write one web application and have it run on a variety of devices is going to mean a much cleaner, less buggy, better maintained experience for everyone. Not all hardware manufacturers can afford to develop and maintain apps for all the major platforms.
Unfortunately right now the only usable implementations seem to be very Google-centric. Getting decent platform support, specifically iOS, is going to be a huge help.
Adding my support for this as well. I'm currently working on a product that uses physical web url notifications. These notifications work out of the box for most Android devices, but on iOS users are forced to download chrome to get this functionality.
Please consider adding support for physical web beacon notifications via Safari!
Since my last post I ended up paying for an app to be made that implements (a reasonable subset of) Web Bluetooth on iOS, so that iOS users can at least use my hardware: https://itunes.apple.com/us/app/webble/id1193531073
However obviously it would be hugely preferable if the functionality came pre-installed (while Chrome on iOS supports Physical Web, it doesn't support Web Bluetooth)
This technology is a must for Progressive Web Applications and IoT.
Is this the best place to get updatse about it's implementation in webkit?
Is there any plan to implement it in the future?
Hello, I work for the Bluetooth SIG.
I'm interested in the potential which a W3C standard Bluetooth LE API for browsers offers, though I not also some of the concerns raised by others. I'd welcome seeing work actively underway between the various parties to see if issues can be satisfactorily addressed. Bluetooth LE APIs are in most other platforms, including the various smartphone platforms. Bluetooth is going to be used increasingly in enterprise computing scenarios and as such, cloud technology with web applications rather than native desktop applications is likely to be the preferred architecture.
Aside from expressing our support, is there anything more tangible which the Bluetooth SIG might be able to contribute? I'd be happy to discuss by phone or face to face.