Dear Jane, we fucked up, sincerely MTA

The piecemeal MTA OMNY rollout is a lesson how not to do a transition from old system to new system. A case where poor design, poor management choices and unanticipated user interaction, each insignificant in isolation, snowball into a nagging long term problem.

The problem goes like this:

(1) Apple Pay Express Transit is opted in by default and iPhone users don’t always know it’s on. They don’t care about using Apple Pay credit cards on OMNY anyway because fare options are limited and OMNY isn’t installed everywhere and won’t be until at least the end of next year. They use good old MetroCard and put iPhone away in the right pocket or purse carried on the right shoulder.

(2) When the user gets to a OMNY fare gate they swipe MetroCard with its peculiar forward swipe motion on the reader which is located above and behind the OMNY NFC reader, which is positioned low and angled at pocket level. As “MetroCard sucks, it may take several (forward) swipes to enter”, the user leans into the gate while doing this and boom: OMNY reader activates iPhone Express Transit and charges fare without the user knowing it.

Default opt in Express Transit has been with us ever since Apple Pay Suica arrived in 2016. But transit cards are not credit cards and everything was fine. Things got sticky when iOS 12.3 introduced EMV Express Transit that uses bank issued credit/debit/prepaid cards for transit on Apple certified open loop systems. Currently these are Portland HOP, NYC OMNY and London TfL.

HOP and TfL don’t have problems with Express Transit. Both systems use contactless exclusively. HOP has stand alone validators, not gates. TfL gates have the NFC reader located on the top. OMNY on the other hand will have MetroCard swipe cards around for years to come: the OMNY transit card replacement is still in development with no release date. With the slow transition pace and current gate design expect the OMNY Express Transit problem to be around until MetroCard is dead, and OMNY is complete with the new tap only card.

In retrospect MTA should have done it this way: (1) rollout out the OMNY card MetroCard replacement first and add open loop support as the very last thing, (2) design better OMNY gates in two kinds, dual mode NFC + swipe, and single mode NFC only. This way MTA stations could do what JR East stations do: start with single mode tap only express gates on the edges and dual mode gates in the middle. As the transition progresses the dual mode gates get fewer and pushed to the sides with single mode gates taking over.

Apple could help by keeping automatic Express Transit opt in only for native transit cards (Suica, SmarTrip etc.). EMV Express Transit should always be a manual opt in. I understand Apple’s perspective: they want to present Apple Pay Express Transit as a seamless one flavor service, not good/better/best Express Transit flavors. The reality however is that the current technology powering EMV open loop fare systems isn’t up to native transit card standards. Apple can’t fix that.

Unfortunately MTA has taken the dumb path of blaming Apple instead of fixing their own problems. New York deserves a world class modern transit system, OMNY is an important step in building one. MTA management performance so far doesn’t inspire much confidence. Let’s hope they focus on the rollout and deliver it without more delays or problems.


Dear Tim

Dear Tim

In uncertain and challenging times it’s more important than ever to look for good opportunities. Here is one for the Japanese market. Did you see that news item from JR East about all those old Osaifu-Keitai models being dropped from Mobile Suica in 2020? That’s a few million upgrade opportunities right there.

How about doing a nice little marketing campaign with the Japanese carriers offering a nice trade in price for those old Osaifu-Keitai with a discount on a iPhone XR or iPhone 8? I know, I know, you only want to sell iPhone XR but until the Face ID camera has magic x-ray ability at an affordable price, all those face mask users in Japan will really appreciate a Touch ID iPhone 8 choice. Offer trade in customers free assistance moving and setting up their Mobile Suica accounts in Apple Pay Suica at local Apple Stores. I’m sure it would be a success.

And while you’re at it offer a nice little replacement campaign for those pesky iPhone X units that don’t work with Suica. There are a lot of Japanese customers who would really appreciate Apple reaching out to help and would probably upgrade with a little encouragement and a bug free iOS 12.

Oh and one last thing, offer a similar little iPhone XR/iPhone 8 upgrade campaign in Hong Kong when Apple rolls out Octopus on Apple Pay. With 33 million Octopus card users in Hong Kong I’m sure it would help iPhone sales there too. Apple has a wonderfully unique global FeliCa strategy tucked away in Apple Pay, used wisely it could be a great sales tool.

Love and kisses,

Ata Distance

Apple Pay Octopus and the iOS 12.1.3 Release Window

UPDATE: Apple Pay Octopus is coming with iOS 13

Note: For simplicity and convenience I have migrated and merged older Octopus related posts here. All new Octopus related developments will be posted separately.

JR East posted a special maintenance schedule this month for Mobile Suica on 1/15, 1/22 and 1/28. The work appears concentrated on the Suica Recharge backend which hopefully points to improved Apple Pay Suica Recharge performance.

I think it also points to something else: a iOS 12.1.3 release with Apple Pay Octopus/Hong Kong transit directions for Apple Maps service around January 29 Cupertino time, early am January 30 in Hong Kong. The timing fits with a full beta test cycle wrap up but more importantly it fits as a kickoff for the Chinese New Year vacation period, good news for an important market to Tim Cook who desperately needs some good news right now.

Go for it Tim! It will undoubtedly help Apple sell more global FeliCa iPhones because Octopus on Apple Pay is a great marketing angle for the iPhone XR/XS models with Express Card power reserve and bulletproofed FeliCa performance. I have yet to experience a single Apple Pay Suica gate error from my iPhone XS with daily use since the launch date.

UPDATE
It occurred to me after posting the above that Apple has introduced transit cards and the technology behind them with larger point releases: iOS 10.1 for Suica (FeliCa) and iOS 11.3 for Beijing and Shanghai Transit cards (Apple flavored PBOC 2.0 ED/EP). In this scenario iOS 12.2 is the logical starting point for Octopus on Apple Pay. However, Octopus is FeliCa which has been part of Apple Pay for over 2 years, Apple has ample engineering and testing experience with the technology to add Octopus with a smaller point release, or none at all which was the case with contactless student ID cards.

UPDATE 2
The original source reports pointed to an end of January rollout, now that iOS 12.1.3 is released we will see how it plays out between now and iOS 12.2. Considering the Apple Pay Suica launch meltdown on iOS 10.1 update day, Apple would be wise to launch on a quiet network day as Apple Pay Octopus day 1 user additions will far outstrip any regular credit card Apple Pay rollout, the use profile for prepaid transit cards is very different.

UPDATE 3
It looks like we’ll have to wait a while longer for Octopus on Apple Pay.

iOS 12 Suica Performance Issues Update

iOS 12/watchOS 5 Suica performance continues to be a very mixed bag for many as Apple closes in on the iOS 12.1.3 update. There are no showstoppers but glitches are constant enough that there’s even an Reddit thread on the subject, a first. Suica performance glitches fall in 4 basic patterns:

  • Suica Express Card error flicker: occasional error flicker at transit gates with iPhone 7, iPhone 8, iPhone X (Rev. B) and Apple Watch 2~4. This is a completely different issue from the iPhone X NFC hardware defect. There is no workaround and will likely be fixed in an iOS update at some point…we hope.
  • Dead Suica Notifications/No Suica Balance Update: Suica Notifications stop working and Suica Balance fails to update at transit gates, store readers and Suica recharges. This affects iPhone 7, iPhone 8, iPhone X (Rev. B) and Apple Watch 2~4 but is easy to fix by putting Suica in Service Mode for a few seconds.
  • Slow or unresponsive Suica Recharge: this is probably more of a backend system issue between Apple Pay iCloud and Mobile Suica than iOS 12 but Apple Pay Suica recharge fails half of the time on the first attempt. This affects all devices and there is no work around except to try again. The Mobile Suica maintenance this month (January 2019) might help.
Suica Recharge works…sometimes
  • Dead Suica Express Card UI on A12 Bionic devices: another case of the hardware works but the software doesn’t that only affects iPhone XS and iPhone XR. Suica works flawlessly on readers but the entire Apple Pay Suica Express Card UI dies: no notifications, no balance update, no Apple Pay sound, no feedback whatsoever. Service Mode does not revive the Suica UI but a restart fixes it. Fortunately this issue seems rare. Unfortunately I have experienced it on 2 separate iPhone XS devices.

UPDATE
Good new: all Suica issues listed above are fixed in iOS 12.3 with great performance.

iOS 12.1.2 Apple Pay Suica Performance Issues

No sooner than Apple issued the iOS 12.1.2 update that JR East pushed out a Suica system notice in their iOS Suica App: When Suica Balance Fails to Update. I guess this really means that Apple still hasn’t fixed iOS 12 Apple Pay Suica performance issues for everybody. My experience with iOS 12.1.2 on iPhone XS has been good so far but it takes time to find out what Suica performance on any iOS release really is. Whatever the case may be, fixing dead Suica notifications and a lost Suica Balance is very simple.

Put Suica in Service Mode and let your device sit for 10~15 seconds, then quit Apple Pay or simply put the screen to sleep. A Suica Notification will then appear with the updated Suica balance. Let’s hope that Apple’s New Year resolution list includes quickly fixing Apple Pay Suica performance issues.