- From: Anders Rundgren via GitHub <sysbot+gh@w3.org>
- Date: Sun, 18 Jun 2017 06:56:58 +0000
- To: public-web-nfc@w3.org
Well, if you "read between the lines", this use case as well as most of the other listed use cases are really about providing Web based alternatives to native "Apps". Although I absolutely love the Web, there are plenty of applications out there that are better served by "Apps". For security related applications like payments you need signed and vetted applications which doesn't have a Web counterpart. However, a viable (and extremely popular), way forward is _combining_ the Web and App worlds since these worlds offer unique capabilities of their own. The recent W3C Web Payment API is the first Web standard of this kind, offering an application specific "bridge" between the two worlds, currently running on Android (for Android Pay and similar). This API will presumably be extended to cope with whatever additional features are needed including loyalty cards. Outside of the W3C, Mozilla and Microsoft are now shipping emulations of Chrome's "Native Messaging" which is a variant on the same theme. It had been pretty cool making a Web NFC bridge but that would require an entirely different project since not even the required hardware is available: https://github.com/w3c/web-nfc/issues/128#issuecomment-308838885. -- GitHub Notification of comment by cyberphone Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/131#issuecomment-309260606 using your GitHub account
Received on Sunday, 18 June 2017 06:57:05 UTC