Those of you who caught Mark Greenfield, Kyle James, and myself on HigherEd Live back in March might recall a brief conversation we had about whether QR codes were more hype than useful. QR codes are an interesting topic that many people either seem really on board with, or really opposed to. Tuesday, Seth Odell brought up the question on Twitter of NFC vs. QR codes over the next five years (Wondering what NFC is? It stands for Near Field Communication. Here’s how it involves RFID.) A very interesting conversation then took place between him, Chris Wiegman, and I that I thought was worth sharing.
Some abbreviated takeaways:
- NFC and QR are different technologies with unique applications, I don’t believe it is fair to discuss them in terms of strict apples-to-apples comparisons.
- NFC has production limitations related to RFID tags it must overcome. QR codes need nothing but a printer and add virtually no cost. Not true for NFC.
- Problems inherent with the use of QR codes deal more with underlying marketing strategy, not the technology. This problem isn’t solved by new technology.
- People that will benefit the most from the use of NFC will be the ones that understand how it compliments QR, and how both technologies extend mobile in different ways.
The following conversation (which you’ll have to use the “Load More” link at the bottom a couple times to get the second and third part of the discussion) has been linearized a tad differently than it took place, to keep some concepts grouped together for readability. Twitter can result in some dang fragmented lines of reasoning when you get multiple people talking about something, believe it or not. I’ve also inserted a few additional thoughts of my own in line, with some helpful links. Feel free to continue the conversation in our comments section below, I’d love to hear your thoughts on the issue.
Finally, I have no idea why Seth’s avatar came through as a sexy lady in a bikini. But I suppose it is an improvement.
Photo Credit: Some rights reserved by scott_bl8ke
The content of this post is licensed: