- From: Zoltan Kis via GitHub <sysbot+gh@w3.org>
- Date: Tue, 24 Sep 2019 15:33:43 +0000
- To: public-web-nfc@w3.org
We should vet the use cases. I wonder if the above mentioned companies would be willing to give up their apps that 1. may collect more data than a web page and 2. which allow them to own the whole solution, whereas with Web NFC a part of the solution is implemented in the browser. However, it's far easier to update a web page than an app. Solution makers could use the Web NFC API and still implement their protocols for `transceive()`, only there would be much less code to write, provided we can offer all the features needed. On that I have some doubt as well, as we've been trying to simplify the native NFC APIs a bit. On the other hand, apps could be scrutinized much more by the app store than a web page, besides it's far easier to take off an offending app than a trapping web page. Of course, origin policy and proper permissions should alleviate some concerns. -- GitHub Notification of comment by zolkis Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/356#issuecomment-534614768 using your GitHub account
Received on Tuesday, 24 September 2019 15:33:45 UTC