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

Hi @scheib thanks for that. There's no doubt that communicating with devices, particularly in an educational context as you've elaborated, is a compelling use case for computers.  Clearly, however, there is a difference of opinion amongst implementers about whether web applications should be empowered to make such connections.

We've reviewed the [Web Bluetooth API positively](https://github.com/w3ctag/design-reviews/issues/139).
  
We've also reviewed the [web serial API](https://github.com/w3ctag/design-reviews/issues/431) - for which we recognized the use case but also we expressed concerns about multi-stakeholder support.

Speaking personally, I'm a big supporter of these APIs. I've personally demonstrated Web Bluetooth on stage at developer events.  I fully get it.  However, as TAG I have to acknowledge that the development of these capabilities has not brought other implementers along.
  
Putting aside the multi-stakeholder considerations, we're not clear on some aspects of the user flow and permission model.  The explainer could benefit from spelling out how a device gets connected, how the permissions are requested, etc... ?

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

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