The user does not need a Mobile Suica account to do this, for example, if you add a plastic Commuter Suica card to Apple Pay. It all works seamlessly because of an arrangement between Apple and JR East that links Apple Pay and Mobile Suica together in a special way.
If you take the time to install Suica App and look your Suica card info, you see something like this:
Let’s say you add a 2nd plastic Suica card to Apple Pay. Look at the Suica App info for the 2nd card and you’ll see something like this:
What’s happening on the system level is that even though you do not have a Mobile Suica account, Apple Pay automatically registers your Apple ID on Mobile Suica Cloud the first time you add Suica card to Wallet, so that you never lose it. If you add a 2nd card it is also registered as Apple ID_1, a 3rd card as Apple ID_2, etc. Each and every Suica card is safe and secure no matter how many times you remove it from Wallet. The important thing to remember is that removing Suica from Wallet never deletes Suica from Apple Pay iCloud or Mobile Suica.
Tsutsumu Ishikawa is probably Japan’s premier tech journalist who came up through the traditional print journalism of Nikkei, kind of like Walt Mossberg or Joanna Stern of WSJ. Ishikawa san was also the journalist who broke the Apple Pay coming to Japan story in the summer of 2016 in the Japanese press, which Bloomberg shamelessly reported in English without giving him credit.
Because of his deep connection to Apple Pay, it’s ironic that Ishikawa san is suddenly tweeting that he’s been bitten by the iPhone X NFC Suica Problem:
Japanese media did not take up the iPhone X NFC Suica problem in 2018. I don’t expect them to now. Even journalists who were aware of the problem like Junya Suzuki, kind as he is, told me, “Let’s leave it up to social media channels.” Unfortunately, in this day and age the reality is that working tech journalists have to pick and choose stories that have legs and get clicks. Otherwise they can’t make a living.
Ishikawa san’s sudden iPhone X Suica problem is intriguing, and worrisome. Is it one of the original problem units manufactured before April 2018? I have no idea, but I have always suspected that all iPhone X units manufactured before the Revision B iPhone X April 2018 switchover will exhibit degraded NFC performance over time.
Other iPhone X users are reporting this too. Even iPhone X device owners who have not had NFC problems are suddenly discovering that their iPhone X NFC is going wonky. I hope this is not a new ugly chapter in the iPhone X NFC Suica problem saga:
I wonder if Ishikawa san and Tanaka san will read this blog and get a Rev. B iPhone X replacement? Probably not, but they should. So should everybody with a problem iPhone X device. I’ll update this post with any new information or developments.
This is unusual because big changes like that are for big updates like iOS 13. I guess Apple decided not to wait for iOS 13 to roll out Apple Card, and made big changes to Wallet starting in iOS 12.2. It will be interesting to see what new Apple Card Wallet functions are offered to developers at WWDC19. My take is that developers will get to do all the things Apple Card does because Apple wants to encourage developers to migrate useful functions out of apps and into Wallet cards.
The dynamic Wallet card art of Apple Card is especially fascinating. One of the problems with static card art in iOS 12 Wallet is it doesn’t do anything and gobbles up precious screen space. Apple Card dynamically changes colors to give the user important information. This dynamic function is very useful and solves some Wallet UI problems.
Suica Commuter cards in iOS 12.3 don’t have enough space to display ‘Add Money’ and ‘Renew’ buttons on the main card along with the commute route. Instead, users have to dig down a level to find them along with the commute plan expiration date. Add Money, Renew, commute plan route and expiration date are important card items that need to be on the main card screen.
Dynamic card art elegantly solves this problem. Suica App already does this in the app by displaying the commute route and commute plan expiration date on the virtual Suica card, just like it does on plastic Suica. Dynamic card art in iOS 13 Wallet would be the perfect solution, all the important items fit on the main card screen. Card art is finally useful and saves screen space instead of wasting it.
Now that full 3rd party NFC access is reportedly coming with iOS 13 tag support for ISO7816, FeliCa and MIFARE, does this mean developers get supercharged Core NFC and PassKit NFC Certificates generously handed out like condoms at a gay sex party? Probably not, the only new things in those rumors are ‘full access’ and ‘ISO7816’, but let’s take a look at some possibilities based on the 3 NFC Forum defined NFC Modes: Card Emulation, Reader/Writer and Peer to Peer.
It’s useful to remember that A12 Bionic powered iPhone is one of the most compelling ‘Global NFC’ devices on the market, with all the important technologies in one package sold everywhere: NFC A-B-F hardware and EMV, FeliCa, MIFARE, PBOC and VAS (value added service protocol) software. Android is fragmented, especially when it comes to FeliCa support.
The big frustration for developers has been that iPhone NFC is all dressed up with no place to go. iOS 12 NFC supports Card Emulation and Reader/Writer but severely limits the Secure Element access necessary for Card Emulation with NDA covered PassKit NFC Certificates, while Core NFC is a limited Reader/Writer Mode sub-set.
The Apple Card UI and Wallet UI design language in iOS 12.2 and later, is so different from the rest of iOS 12 that I’m surprised nobody in the Apple tech blog space picked up on it. There are lots of useful card options and information that can be piped into Wallet cards from the card provider cloud, instead of sitting in a separate app.
This applies to card artwork as well. Static card artwork in iOS 12 doesn’t do anything and gobbles up precious screen space. The dynamic Apple Card UI and artwork convey important information to users while solving the wasted space problem.
I do have one more wish for the iOS 13 Wallet UI: please integrate the separate iPhone and Apple Watch Wallets into a single Wallet. It’s incredibly convenient to control all transit card recharge/reload and other options on iPhone instead of fiddling with the tiny Apple Watch screen to recharge a Suica card for example. Suica App manages separate Suica cards on iPhone and Apple Watch incredibly well in one place.
Easy Card Emulation: I am less sure how Apple plans to make card emulation easier for developers:
New functions in PassKit that do more
Less stringent and easier to obtain PassKit NFC Certificates
A combination of the two or
Something new altogether
I hope for a combination approach that keeps everything secure while making it easy for developers to add all kinds of non-EMV cards to Wallet, the major categories include…
Regular Reward Cards: There are tons of these everywhere, mostly mag strip. My real wallet has JRE POINT, WAON POINT, Tomod’s, plus a crazy collection of stamp/point cards. How nice it would be if it was super easy for developers to port these to Wallet with NFC capability.
ID Cards: This is where ISO7816 tag support fits in. Contactless Student ID cards in iOS 12 were a MIFARE only custom in-house job, transit cards without transit, by Apple in cooperation with Blackboard. Hopefully Apple will greatly extend ID card support in all NFC flavors for many companies and institutions, for all manner of ‘company only’ Wallet ID cards.
Android has a huge advantage over iOS because Android apps have the NFC access to do what they want. From RFID Insider:
Below are all the abilities/formats available for writing to a tag:
Business Card Link/URL Wi-Fi Bluetooth Email Telephone Number Geo Location Launch an Application Plain Text SMS
A fully functional Core NFC could do all this, but the important question is how would Apple want to do all this. NFC tags are great technology but they remain deeply geeky for the majority of users. The key is making NFC tags as friendly, easy and secure to use as Apple Pay. This is exactly what Apple plans to do.
The easiest way to think of it is that instead of tapping a dedicated NFC reader to pay with Apple Pay, NFC tag Apple Pay turns your iPhone into the reader. An NFC tag and iPhone is all that you need to Apple Pay at a store.
What does this sound like to you? Yep, this is exactly what QR Codes do and NFC tag Apple Pay is aimed right at the ‘but the store doesn’t need an expensive NFC reader to use QR’ sweet spot that QR Codes have occupied up to now. NFC tag Apple Pay levels the play field, neatly eliminating the QR advantage while offering security that QR Codes cannot match.
However don’t assume that the QR players are chained to QR Codes, it’s an inexpensive and convenient technology for building payment system app services, nothing more, not particularly sacred. NFC tag Apple Pay works in an app and this offers Japanese QR Code payment systems such as Line, PayPay, etc., a way to incorporate Apple Pay NFC support in their app, if they choose to do so.
A12 Bionic iPhone XR/XS are the only devices that support background NCF tag reading and the native ability to read tags without an app. The big question in my mind is how Apple plans to implement NFC tag Apple Pay on older devices
Peer to Peer
iOS 12 does not support NFC Peer to Peer. I don’t see that changing in iOS 13 if it can’t be part of a new Apple Pay service. AirDrop already works well across devices that do not have NFC capability. That’s probably enough real world peer to peer for most people.
The Apple Pay theme for WWDC18 was ‘move Passes into Wallet, get rid of the QR Codes and replace them NFC.’ The new Apple Card UI improvements in Wallet and NFC tag support suggest the Apple Pay theme for WWDC19 will be: ‘move card functionality out of apps and into Wallet cards with new iOS 13 PASSKit controls, or get rid of apps altogether and replace them will all kinds of NFC enabled cards and NFC tags.’
It certainly makes sense. Apple Pay is NFC for the majority of iPhone users, the NFC thing that people use. Apple devoting iOS resources into making card emulation easier and better for 3rd party developers to add all kinds of cards to Wallet, and migrate functions out of separate apps to the Wallet card itself, will give the most bang for the development buck. NFC tag Apple Pay will finally bring NFC tags into the mainstream while eliminating the remaining advantages of QR Codes. It’s going to be a very interesting WWDC for all things Apple Pay.
There are very few Apple Maps rumors for WWDC this year. All we have is one little paragraph from Mark Gurman:
An updated Maps app will make it easier to set frequent locations, like home or work addresses, and then navigate there. Users will also be able to create groups of frequent places and add a photo to them. The current interface for navigating to suggested or past destinations can sometimes be confusing. This will increase competition with Google Maps and Waze apps
The current interface for navigating to suggested or past destinations can sometimes be confusing? (Duh!) Increase competition with Google Maps and Waze? (Really?)
Collection Eddy Cue outlined Apple Maps 2.0 as a dual approach of using anonymous iOS device data and Apple Maps vans to collect high quality map data while getting faster updates from devices vs. the next scheduled drive:
“The truth is that Maps needs to be [updated more], and even are today,” says Cue. “We’ll be doing this even more with our new maps, [with] the ability to change the map in real time and often… In the new map infrastructure, we can change that relatively quickly. If a new road opens up, immediately we can see that and make that change very, very quickly around it…”
In short: Traffic, real-time road conditions, road systems, new construction and changes in pedestrian walkways are about to get a lot better in Apple Maps.
TechCrunch Apple is rebuilding Maps from the ground up June 29, 2018
High quality in-house map data collection is a vital step, but there are limitations. The Google Maps Japan meltdown proved that even Google can’t do it all. When Google dropped premier Japanese map data supplier Zenrin, Google Maps Japan quality instantly crashed. Japan has very high density urban areas and very remote rural areas that cannot be effectively mapped from a van no matter how much fancy recording equipment it has. Zenrin has a 1,000 person ‘ground truth’ team just for mapping those kind of places on site, on foot.
Processing Panzarino explained at length how the high-resolution image data collection effort fits with Apple’s in-house data qualification toolkit to identify problem areas with machine learning, so that the human team can quickly vet problems and update corrected map data for the trouble area:
The coupling of high-resolution image data from car and satellite, plus a 3D point cloud, results in Apple now being able to produce full orthogonal reconstructions of city streets with textures in place. This is massively higher-resolution and easier to see, visually…This is hugely important when it comes to the next step in Apple’s battle for supremely accurate and useful Maps: human editors.
Apple has had a team of tool builders working specifically on a toolkit that can be used by human editors to vet and parse data, street by street.
Many hundreds of editors will be using these tools, in addition to the thousands of employees Apple already has working on maps, but the tools had to be built first, now that Apple is no longer relying on third parties to vet and correct issues.
And the team also had to build computer vision and machine learning tools that allow it (Apple) to determine whether there are issues to be found at all.
There we have it: Apple is using in-house machine learning and no longer relies on 3rd party vetting or correction. How is this working out? Answer: not so great. At least in Japan. Let’s take a quick look around the Ikegami Honmonji Temple area.
Example #1: Ikegami Hall is completely missing in the map view even though it is in the satellite view.
Example #2: Duplicate Five-story Pagoda pin locations. The Manji character marked pagoda is correct while the grey one from Foursquare is the wrong location and duplicate information that needs to be removed or merged. <Kudos to Apple here for respecting local culture and using the traditional Buddhist temple Manji character, while Google Maps resorts to censorship>
The conclusion here is that Apple Maps 2.0 isn’t living up to Eddy Cue’s stated goals, at least in Japan:
In example #1 machine learning is supposed to identify problem areas when the satellite and map views don’t match up, but fails. The human team is not alerted to the problem and cannot fix it.
In example #2 the system cannot distinguish between incorrect 3rd party supplied duplicate data and the real thing. In my experience Foursquare Japan and Yelp Japan have no human location vetting, most of their product is worthless. Apple faces a choice: is it better to show nothing, or is it better to show unvetted 3rd party data that has a high risk of being incorrect leading users to the wrong place? My suggestion: don’t use any 3rd party data that has not been vetted by Apple Maps van collected in-house map data.
Presentation Cartography and the Maps UI is where it all comes together.
Apple has a team of cartographers on staff that work on more cultural, regional and artistic levels to ensure that its Maps are readable, recognizable and useful.
For instance, in the U.S., it is very common to have maps that have a relatively low level of detail even at a medium zoom. In Japan, however, the maps are absolutely packed with details at the same zoom, because that increased information density is what is expected by users.
Panzarino got it wrong here. Users in Japan don’t want a map view packed with details. The difference is not cultural, it’s simply that high density metropolitan areas like Tokyo have much more information packed into a given area than American cities. Presenting high density information in clean easy to read cartography is challenging.
Yahoo Japan Maps and Google Maps have both evolved their cartography away from detail packed views to cleaner cartography. Yahoo Japan Maps cartography is the best because they deploy good design with smartly edited zoom level assignment: this information is important at default zoom level, this other information belongs at zoom-in level 2, etc. This clean approach shows only the important details for the given zoom level for quick navigation. The differences in readability comparing Tokyo area views of Yahoo Japan Maps, Apple Maps and Google Maps are immediately noticeable. Here is Gotanda Station:
Apple Maps 2.0 fails here too. The cartography is less readable, recognizable and useful than the competition. The easiest fix would be for the Apple Maps cartography team to stop stuffing so much information at the same zoom level and intelligently rank information to display at different zoom levels.
Unfortunately, that effort requires a group of humans with expert local area knowledge. An Apple Maps engineer explained the dilemma to me once, “Yahoo Japan Maps has the luxury of focusing all of their product development on just the Japan market.” It’s a luxury that neither Apple nor Google have.
WWDC19 Wish List
Here is my wish list for Apple Maps Japan 2.0 using the same categories, including transit which is a separate app and service layer within Maps.
Traffic and Real Time Road Conditions: these important features are missing in Japan and absolutely must be added. Car navigation with Apple Maps in Japan is worthless without them.
Offline turn by turn navigation: Apple Maps turn by turn navigation completely dies in underground roads or in rural areas without a network connection. It’s like flying blind. Dedicated Japanese turn by turn navigation systems handle this without a problem. Apple Maps 2.0 needs to match the same level of performance to be a reliable car navigation service.
Fix stuff: Improve machine learning to identify problem areas for humans to fix, or hire humans who can identify and fix problems in Japan maps.
Vet Stuff or Don’t Use It: If Apple Maps cannot internally vet 3rd party social networked geo trash from notoriously unreliable Yelp, Foursquare and TripAdvisor, don’t use it.
Presentation(Cartography and Maps UI) This is where most of the action is covering how the map looks and how users interact with it.
Apple Maps Cartography 2.0 Google Maps and Yahoo Japan Maps constantly tweak and evolve their map design, changing contrast, colors, text sizes, and more while pushing map information updates. Meanwhile Apple Maps cartography is fossilized in 2012 debut era design garb. I can only assume 2 things. Either Apple thinks so highly of the current Apple Maps cartography design language that it will never change it. Or Apple is creating a whole new cartography design. Let’s hope for the latter.
Fix the information overload: with smarter zoom level editing
Eliminate Separate Map View/Transit View Modes Toggling back and forth between 2 basic view modes in Apple Maps is passé. It desperately needs a revamp. Yahoo Japan Maps leads the way here by collapsing separate road map and transit maps into a single comprehensive map view that covers 99% of what users need, while offering a real rail map for the 1% who need a real rail map. It’s a time saver and smart way to eliminate toggling map views. More on this in the transit section.
Recents2.0 The current version of Recents is an old shoebox filled with crap: tapped places, liked places, Siri searches, suggestions, liked train stations to receive train delay notices, home, work, and stuff I have no idea why it’s even there. There are so many improvement suggestions I don’t know where to start. I’ll keep it simple and say, Apple please figure out what Recents is supposed to do, so that we don’t have to.
Nearby2.0: Nearby suffers the same problems as basic processing, Apple Maps 2.0 needs to do a better job of filtering out the junk. Anybody can list 10 nearby cafes, but only smart editors can give me 10 that are worth visiting. Also follow Yahoo Japan Maps nearby approach of keeping everything on one screen, with minimal pinch and zoom. Avoid Google Maps approach of turning Nearby into stealth advertising.
Live Weather Layer: this is Yahoo Japan Maps insanely great secret weapon. I always use it to find when its raining and where, with a time slider to predict if I need an umbrella at my destination. It’s a life saver and must have Apple Maps 2.0 feature. Once you use it, you can never use another map that doesn’t have it.
Nearby Transit Time Widget Google and Apple both use the same transit data supplier, but Google Maps uses it much better than Apple Maps. Most people already know where they are going and how to get there. What they really want to know is: when is the next train? Google Maps does this via a handy widget that offers location based nearby station train times and bus times without having to open the map or tap on a station. This is incredibly simple and convenient. Apple Maps 2.0 needs to offer it.
Siri Transit Support Siri does not support transit requests. Siri can navigate you to the nearest station but after that you are on your own. The ability to ask Siri for transit times is an important Apple Maps 2.0 feature.
Transit Route Search 2.0 This is another area where Apple Maps has stood still while Yahoo Japan Maps and Google Maps continually push out improvements: route suggestion sorting by fare, transit time and number of transfers, train car position information for faster transfers and exits. Apple Maps 2.0 Transit needs to catch up with the competition.
Location Based Transit Alarms on iPhone Apple Maps transit has wonderful integration with Apple Watch but it could be improved with destination and transfer point alarms/alerts that also work on iPhone.
Improved Apple Pay Transit Card Integration Apple Maps has some basic integration with Apple Pay Suica but it could be improved by incorporating user Suica Commute Plan information for better route searches with more accurate fare information. Apple Maps integration with HOP and Ventra cards in Apple Pay Wallet would be a great feature for those transit regions.
Adaptive Transit Times The problem with transit route suggestions on Apple Maps, Google Maps and Yahoo Japan Maps is that once the user selects a route suggestion, transit times are locked in and cannot change on the fly. All too often a users selects a route and time but catches an early or later train, and has to input a new search to reset the transit time. But this is often impossible to do on the fly as transit route searches add a ‘time to station’ buffer. Transit times that adapt and automatically update to transit conditions would be a great feature to have in Apple Maps 2.0 transit.
We’ll see what, if anything, is delivered for iOS 13 Apple Maps 2.0 at the WWDC19. Keynote on June 3.