Re: [w3ctag/design-reviews] Bluetooth RFCOMM in Web Serial API (Issue #854)

Re cynthia, maxpassion: "compelling user story where this would get mass adoption": I've already seen this by walking into a school and seeing https://vex.com robotics being used - they're [used widely](https://www.vexrobotics.com/competition). Google also showcased the similar https://spike.legoeducation.com/ this year at Google IO & Connect events. 

People expect computing technology to work, even if infrequently.  Serial has a variety of applications from education, home automation, enterprise/industrial, maker, and common consumer devices. These range from frequent daily use (e.g. point of sale devices, inventory tools, industrial sensors) to infrequent (e.g. configuration of consumer devices).

In the TPAC 2022 Breakout session Device APIs (Bluetooth, HID, Serial, USB) [slides](http://goo.gle/tpac2022-device-apis)[ (PDF copy)](https://lists.w3.org/Archives/Public/www-archive/2022Sep/att-0017/device-apis.pdf) I discuss the adoption at a larger scale. In the year since that presentation Serial usage has peaked at more than 4 times the usage we'd seen previously.

Bluetooth RFCOMM is a request the Chrome team has had from multiple partners, the top two that come to mind are in education and consumer devices, with weekly and monthly frequency use cases respectively, both from highly recognized global brands.  Their devices already use Bluetooth RFCOMM protocol and they won't be changing the hardware/firmware for these.  For the web to meet the need we are implementing this approach.  The alternative is that developers like these meet the user's needs with e.g. windows apps or fail to meet the needs on Chromebooks.  Even on Windows, partners indicate the high value of e.g. not requiring teachers/children to try to install and manage other applications vs just using the web app.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/854#issuecomment-1699993167
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/854/1699993167@github.com>