- From: Kenneth Rohde Christiansen via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 Apr 2020 12:51:50 +0000
- To: public-web-nfc@w3.org
Use-cases === TNEP allows for device communication like Bluetooth and USB does. It is not high bandwidth like USB so it is probably more comparable to Bluetooth. The big difference is that it requires close proximity to the device which is better for privacy: * others cannot gain access from a distance * easy to identify who you are communicating with Also keep in mind that there is a new NFC Handover Record for Bluetooth LE that allows to handover communication to Bluetooth if requires/advantageous. Examples -- Today with my smart valves, I have to connect to the devices remotely (Bluetooth or Mesh network) but I need to press the valve to enable Bluetooth broadcast and additionally for the valve to show a number so that I can identify who I am talking to. All of that would be solved with TNEP and NFC. First tap to the valve could load the URL to the web app (common NFC record) and a second tap allows me to get additional info from the valve as well as start a bluetooth handover. Potentially one tap would be all that is requires if we allow loading and then immediately share the read data with the web site as it instantiates a `TNEPReader` - but that is an implementation thing. My smart valve might have a lot of info to share, like humidity and temperature over some time period, and using TNEP it would be possible to immediately share this info with the reading web app without Bluetooth and so on. Example 2 --- A technician needs to debug a machine and can immediately read the machine info as well as debugging info using a simple TNEP enabled web app. -- GitHub Notification of comment by kenchris Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/567#issuecomment-620586449 using your GitHub account
Received on Tuesday, 28 April 2020 12:51:52 UTC