Open riju opened 5 years ago
There is basically:
So there seems to be
NFC-A, NFC-B, NFC-F, NFC-V and ISO-DEP - maybe there is a Mifare thing as well
Judging from the Android APIs, working with these protocols requires more or less the same APIs
This is related to https://github.com/w3c/web-nfc/issues/238 - Riju if you can come up with a complete API proposal based on top of that and the current Android API, that would be a great start
Any update on this one ?
Hi,
I'm also curious if there's been any development in this area - web-nfc adopting these protocols. Is there any road map for that?
I work for an identity verification company and we verify ID documents digitally, which include NFC-enabled passports and ID Cards. Since the pandemic, there's been surge in usage of those kind of services, which can provide safe and secure means of checking identity. Most reliable/accurate way is by verifying data stored on the chip. That requires ISO-Dep & NFC A-B protocols, for which we currently rely on native apps. But increasingly the trend is to provide same functionality via web journeys.
Have we gotten anywhere with this? Feels like the whole in-browser NFC reader wave has come to a complete standstill.
Any update on this?
Looks like a lot of folks want to read the information in their travel cards which can be read by native NFC apps and special NFC apps built for those cards. Internally they are using NDEF for maybe a handshake but reading/writing is being done using IsoDep atleast for the travel cards in Finland. Supporting this use case means we have to implement
transceive(byte[])
and that will change the API shape a bit and also we might need to revisit our Permissions and Security model.Let's harvest some protocols used in other countries, so that if/when we decide to support this use case, we can make an informed choice.