Re: [web-nfc] Change default compatibility value to `any` (#299)

> I still think* web developers want to simply interact, by default, with "any" NFC tag.

That might be, but it is a bit against the web, where we try to make solutions that work everywhere and not push proprietary formats. @reillyeon

> Is NXP Mifare Classic being only readable/writable by phone with a NXP chip the reason why every new web developer will have to use compatibility: "any"?

I don't follow. If developers buy actual NFC chips they don't don't need to worry or care, it will just work out of the box.

If they choose to buy Mifare Classic because of price or legacy systems etc, they should be aware that these tags will not be readable by all users and that might cause a lot of trouble - hense the current opt-in.

From working with NFC, regular devs have no idea that they cards or tags they bought might not actually be NFC compatible, and it is a costly affair finding out after that you have rolled out a product that certain phone users cannot interact with your cards/tags because they were proprietary in nature.

Even a bus system of a certain country that I know ended up using mifare classic public transportation cards and now that is delaying the whole transition to payment by phone.

In a way you could argue that being a web standard we should only support NFC Forum tags as that brings no tie-in to proprietary systems, but as Mifare Classic is deployed many places, we opted to add the 'compatibility' fields so that people could explicitly opt into using it, knowing all the downsides.

-- 
GitHub Notification of comment by kenchris
Please view or discuss this issue at https://github.com/w3c/web-nfc/pull/299#issuecomment-522558117 using your GitHub account

Received on Monday, 19 August 2019 12:49:15 UTC