If you are thinking about trying iOS 13 Public Beta 2 (17A5522g), don’t. Developer beta 3/public beta 2 is usually a point when things settle down and come into focus. Not this time. The first iOS 13 developer beta 3 build (17A5522f) was almost solid enough to recommend. After installing yesterday’s seemingly minor ‘g’ build release, my iPhone XS mini-reboots itself more than 10 times a day: whatever I am in the middle of, the screen goes dark, the refresh icons twirls, 5~10 seconds later I’m looking at the lock screen.
Unless you are really horny, don’t screw around with the iOS 13 betas, all of them. Wait for the official release, or better yet the first point release.
Apple’s strong point is the tight integration of software services across different devices that no other platform can match. Apple Pay Suica works on iPhone and Apple Watch, but the latter combination of technology, function and size makes it a completely different and beguiling experience. Apple Pay on Apple Watch is its own special thing.
A Temporary Split in the NFC Evolution Line? The evolution of Apple NFC on both iPhone and Apple Watch was in lockstep up until the arrival of A12 Bionic in 2018. The A12 Bionic NFC powered background tag and Express Transit power reserve features only work on iPhone XS/XR. Apple Watch Series 4 does not support these NFC features, nor does watchOS support the Core NFC framework, this means that NFC tag Apple Pay on Apple Watch is out of the question.
Is the feature split temporary or does it represent a different line of NFC evolution for Apple Watch? The absence of Core NFC makes sense because watchOS does not support 3rd party apps, at least not yet. Express Transit power reserve however, would be a great feature to have on Apple Watch as iOS 13/watchOS 6 Apple Pay Express Transit rolls out to Chicago Ventra, Brisbane myki and Hong Kong Octopus.
Getting that feature on Apple Watch depends on how quickly Johny Srouji’s A team can implement the A12 Bionic Secure Enclave design that handles basic Apple Pay transactions directly and bypasses the OS, on the S Series chip. I cannot believe they are not pushing hard to deliver the goods as soon as possible, perhaps even with Apple Watch Series 5 featuring a S5 Bionic chip.
Delivering a S5 Bionic would get Express Transit power reserve on Apple Watch with NFC performance gains as well. It would also give Apple the option to add NFC background tag reading later on as watchOS becomes more powerful and independent.
The iPhone 7 FeliCa Question There is one fuzzy area of iOS 13 Core NFC and it is iPhone 7 FeliCa support. At WWDC19 Apple announced that all devices, iPhone 7 and above, would support the enhanced NFC tag lineup: NDEF, FeliCa, MIFARE, ISO 7816, ISO 15693, VAS. But this does not match up with Apple’s own device specs for adding a FeliCa Suica card to Apple Pay:
Apple is telling developers that all iPhone 7 models are good for FeliCa but telling customers that only iPhone 7 JP models are good for FeliCa. This means we get one of two scenarios:
iOS 13 retroactively adds FeliCa support to all non-JP iPhone 7 models. Apple can do this by adding device specific FeliCa keys as iPhone 7 NFC hardware is the same for all models worldwide.
iOS 13 Core NFC FeliCa tags work but non-JP iPhone 7 models (without FeliCa keys) do not work for FeliCa transactions at the terminal.
The latter ‘FeliCa keys vs. No FeliCa keys’ scenario is illustrated in a comment post by Reddit user FelicaDude, if I understand correctly, that without device specific FeliCa keys iPhone 7 only works in basic Read/Write mode without encryption, with FeliCa keys iPhone 7 works in Read/Write encryption mode necessary for local offline processing with payment terminals (i.e. Suica):
The international iPhone 7s can do basic FeliCa read/write without encryption, because they embed a FeliCa-capable CLF <contactless frontend>. Apple has chosen not to provision them with Osaifu-Keitai keys, probably to avoid paying royalties to FeliCa Networks for each device.
It’s a very good question. Finding the reasons behind the manufactured QR Code in Japan mania is not easy. On the surface it looks like a strange retro attempt to replicate the success of AliPay and WeChat Pay in the Japanese market and lower operating costs are certainly part of the allure. A close examination of actual QR use boils down to LinePay and using LinePay points to buy stuff on the Line Store (stickers, coins, etc.).
So why is 7-Eleven aiming to trash their FeliCa nanaco card and push their user base to 7pay QR, and why are all the other convenience store chains doing the same? IT journalist Junya Suzuki, Japan’s top reporter covering all things cashless has posted a great explanation: Big Data.
If you have lived in Japan for any length of time you are probably familiar with the T-Point card. A few years ago Doutor, FamilyMart and many other business were pushing T-Points. Now they are not. Doutor dropped T-Point for Docomo d POINT in June, and the arrival of QR FamiPay is FamilyMart kissing T-Point goodbye.
As Suzuki san points out, from the convenience store point of view, the problem with customers using Suica, nanaco or T-Point is that they don’t have personal data attached to them. Anybody can buy a Suica card at a JR station or a nanaco card at 7-Eleven and use it on the spot. The only piece of data going into the system is the card id#. They can’t get your name, phone, etc. and profile the customer.
With QR Code apps and an account signup/sign in, QR Code platform operators get the information they want to profile customers and plug it into Big Data. The customer ends up being the product. It’s not about offering better service or technology. How useful QR Code payment apps are in the long run, or how much they actually end up being used, is anybody’s guess.
Unfortunately the current messy situation is only going to get worse as Japanese bank QR Code platforms start launching this fall. Smartphone users will have to find their own way through a growing maze of QR payment apps and different UIs, each one vying for attention with campaign booty. The freebie startup campaigns will eventually end, The inevitable consolidation process will be painful. There is no doubt however that the 7pay startup fiasco is a tipping point, the reevaluation process has begun.
Just a friendly reminder that the first of JR East’s major Suica system maintenance downtimes starts Saturday July 6 at 9pm and runs to 5am. Mobile Suica and JR East station Suica ticket machine services are going offline.
I think we are witnessing the QR Code tipping point in Japan. After yesterday’s 7pay ‘latest in a series of QR Code payment system security meltdowns’, IT journalist Tsutsumu Ishikawa tweeted, “It’s time to promote FeliCa for Japanese cashless.” Ishikawa san also retweeted Twitter user S: “QR is so over,” who goes on to say that the low bar QR Code entry point only resulted in incompetent players setting up payments systems. The resulting mess and confusion ends up destroying the very cashless migration momentum the industry worked hard to create.