NFC: What we Have Now
In iOS 11, Apple introduced the CoreNFC framework to iOS. This allows developers to detect and read NFC tags that contain NFC Data Exchange Format (NDEF) information. The iPhone can read messages, but can’t communicate back. It could be useful to see details on a product, museum display, or get run information from a treadmill, but little else. It also required an app to be open and user authentication within that app. Developers haven’t been impressed.
Apple’s limitations on third party NFC access makes it useless to third party developers. Developers haven’t wanted to do the work required to implement Apple’s limited framework. A QR code can also read information, and doesn’t require special hardware. QR codes are easier to implement as well, and they’re cross-platform.
What we Could Have
Android users have long known the benefits of NFC. They can do peer to peer exchanges of information and payments, open hotel rooms, and pay for their fare on the train. Many metro systems all over the world use NFC, and NYC is planning on implementing it… eventually (getting Cuomo’s MTA to do anything good is like pulling teeth from a hungry alligator with a pair of tweezers). In the UK and Japan, Android users can pay for their metro tickets with their phones. Perhaps that’s one of the many reasons why iPhones are less popular outside of the U.S.
Apple wants to change this. iOS 12 will finally make NFC on the iPhone useful, according to The Information. In fact, they’re already testing it, using their employees as test subjects. At Apple’s new Apple Part campus in Cupertino, Apple employees can gain access to buildings using their iPhone. Simply tapping their iPhones next to a door can unlock the door. This is how it would work for iOS 12 users. They wouldn’t need a specific app, they could just tap their phone to devices, and, if they have the proper authentication, gain access to a room or pay for a ride.
Could this be Problematic?
Apple has, for years, stated that NFC could be a target for hackers. They’re right, in the same way that having WiFi enables hackers. Apple and third party developers can—and would—implement strict security protocols. They could lock the phone down to unrecognized NFC activity, for example, and require user authentication for any actual transactions, such as Apple Pay. In the case of metros, users could load up a card with money for their rides, and then not have to worry about authorizing the turnstile’s transaction from this pool of money. You could even set daily limits, perhaps no more than $10 spent on the metro per day without authentication, securing your commute. With proper authentication between devices, NFC can be done securely, without user interaction beyond tapping a device to another device.
However, Apple’s NFC does still have a few bugs. For example, when I had NFC turned on my HTC U11, if I placed my iPhone on top of it, it would try to activate Apple Pay, thinking I’ve placed my device on a terminal. This is because all NFC activity is defined by Apple as being for Apple Pay. By opening the chip up to third party developers, Apple would fix this issue. Until then, I keep NFC off on my U11, just so it stops confusing my poor iPhone.
Is this Likely?
This is certainly one of the more likely Apple rumors I’ve heard. iOS 12 is set out to be a disappointment, but an easy to implement feature like NFC access could help give Android users a reason to consider an iPhone. The lack of NFC access would likely turn away anyone who uses their smartphone for metro access, so this could be a huge win for Apple. Furthermore, it wouldn’t be too difficult for Apple to secure, as long as they continue to require TouchID or FaceID for any actual financial transactions. While iOS 12 looks to be a small update, third party NFC access could be a considerable selling point for the platform. I suspect this rumor is valid, and NFC access is immanent. We’ll know more after WWDC, which starts on June 4th.
Source: Benjamin Mayo, 9to5Mac