Actually, interestingly, QR codes can be better for some payment scenarios than NFC.
I live in China and I can go to my local corner shop, pick up a bottle from the fridge, and even if there's a queue at the register I can scan the code from a distance, pay and leave with a nod from the shop keeper.
QR codes are also used for exchanging contact information... when I give a talk in China, I put my Wechat QR code at the end so any member of the audience can scan it from the slide for follow-up conversations.
> I put my Wechat QR code at the end so any member of the audience can scan it from the slide
I've always been surprised by this (and even more by QR codes in magazine ads and billboards). I'd think that these days, for 90% of applications a regular URL should work. Just as your photo app thee days marks (and often labels) the faces, it could simply highlight all the URLs, email addresses etc in the image and let you click on them.
Yes, QR codes are more robust (at the cost of a small payload for a large image) but I suspect in most cases it's unnecessary.
QR Codes do work rather well actually in different contexts, they are very robust. Upside down, from across the room, weird lighting...
Also, in the Chinese context, everybody knows what to do with it and what to expect to happen if they scan it.
The farmer coming into the city on a trike selling fruit even accepts payment by QR code :)
I completely agree, especially on roadside billboards. URLs have the excellent advantage of supporting 'human storage' - i can remember a URL and try it later. QR codes, not so much.
QR codes are cheaper, but NFC tags are more convenient. QR code are typically also all the same on a given label, where NFC can be programmed to have a unique id for each relatively simple.
QR codes support multiple devices at the same time, and have much larger range for reading (limited by the physical display size). Unique ID's can be built into the app reading the QR code for things like payment transactions. If I control the app reading the QR code (like WeChat), I can easily add state and add some "ping-back" behaviour to ID who/what/where the scan happened.
I think you misunderstood. I never talked about ping back or anything like it. For that, both are exactly the same. I was purely talking about how it scales when you need to identify each item individually, for instance library books. But it wasn't exactly clearly communicated, my bad.
For inventory management, it's preferable that each item has its own unique code. So either you need to print a different QR code for every item, or you put on an NFC chip.
It is true that QR codes are supported on more devices, but that is because cameras and screens are ubiquitous with smart phones. An NFC reader is cheaper.
Indeed, but they are already printing a label for every parcel, and they used barcodes long before NFC tags was a thing. They already have hardware and tooling in place for it, so unless NFC will save them a significant amount of money it makes no sense to switch.
Think of a stockroom. When you get new inventory, you put on an NFC tag on every item, and then you have to register each which is just one sweep. With QR/barcodes you either have to register and then print and put on the items, or you have to scan each individually after.
Both NFC and QR have strengths and weaknesses. I'm certain that we will see both utilized more and more.
QR codes are also used for exchanging contact information... when I give a talk in China, I put my Wechat QR code at the end so any member of the audience can scan it from the slide for follow-up conversations.