- From: Anders Rundgren <anders.rundgren.net@gmail.com>
- Date: Wed, 1 Mar 2017 13:14:59 +0100
- To: "Web NFC (W3C)" <public-web-nfc@w3.org>
Since WebNFC doesn't do the obvious (create a paired BLE connection between the invoking Web page and a mobile device), the industry have turned to QR code for applications like Web payments and Web identity. A drawback with the HTTP calls used by the (native) apps is that they do not support interactivity in a nice way. Although I have yet to test this, it seems that QR used for bootstrapping a WebSocket server connection would do the trick. In my take on the matter the QR will also provide some kind of App ID so that a single QR App can not only provide the HTTP URL but invoke the desired App as well. The communication itself could (after WebSocket establishment), for example use https://cyberphone.github.io/doc/web/yasmin.html which is designed for event based protocols. Anders
Received on Wednesday, 1 March 2017 12:23:09 UTC