- From: Mark R. James via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Mar 2018 18:43:46 +0000
- To: public-web-nfc@w3.org
Currently, QR is the only way for a website to transmit a URL from iOS, because there are no indications of WebNFC being implemented in Safari. QR is also the best way to receive a URL on iOS, because it's built-in to the iOS 11 Camera app (iPhone 5S and above), while only iPhone 7 and above supports the triggering of a browser action from a URL sent by NFC. On Android, easy inbuilt support for URL reception and browser triggering by QR code is much less widespread. But conversely, support for URL reception and browser triggering by NFC is much more widespread than iOS. Chrome on Android is still the only prospect for transmitting URLs from a website via NFC to both Android and iOS devices. But WebNFC is still both unreleased for general use, and lacks support for peer-to-peer URL sharing. I first [expressed interest](https://lists.w3.org/Archives/Public/public-web-nfc/2015Sep/0014.html) in such support in September 2015. On the surface, NFC seems to be a more reliable and less awkward means of URL transmission than QR codes, but I've been impressed with QR's ability to decode rough photos of on-screen codes. Both take-photo and tap-payment are widely-familiar phone actions. -- GitHub Notification of comment by mrj Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/141#issuecomment-373808832 using your GitHub account
Received on Friday, 16 March 2018 18:43:52 UTC