Are Google Pixel 5 and Fitbit up to the Global NFC Challenge? (Update: Pixel 5 not)

It’s that time of year again to think about FeliCa support on the Google Pixel platform as Pixel 5 approaches. Ever since Pixel 3 things have been the stuck in a rut: the same global NFC (A-B-F) chip and Mobile FeliCa is in all Pixel models, but only Osaifu Keitai apps launch and run on Japanese SKUs. No Suica for you if you don’t have one of those.

I used to think that Google was going cheap instead of deep. Google is cheap here actually, and lazy, but there are some other reasons. It goes back to the problem many people had with Google Pay Japan FeliCa support to begin with: it’s only a UI candy coating on top of the aging Osaifu Keitai stack and apps. Instead of doing a true top to bottom Google Pay global NFC solution like Apple did, Google Pay Japan FeliCa support is just surfing on the Osaifu Keitai board. And of course the Android Pay HCE-F thing is long since dead, it’s eSE or nothing now.

One problem is this: Osaifu Keitai is a domestic platform, Osaifu Keitai apps (Suica, etc.) are domestic apps. The various Osaifu Keitai partners and developers don’t want to deal with the extra expense of multi-lingual localization and support. Neither does Google, hence the logjam.

Google’s recent purchase of Fitbit might be the agent of change that finally changes the situation. The Osaifu Keitai model doesn’t extend to wearables. Google Pay has to come up with something new to replace Fitbit Pay, something that works across paired devices seamlessly if Google Pay Suica is to exist on a Fitbit smartwatch paired with Pixel.

There is something new this time around that didn’t exist, or at least didn’t exist as a marketed developer product back in 2018: Mobile FeliCa Platform and Mobile FeliCa Cloud for supporting all kinds of Mobile FeliCa services worldwide. This arrangement got us Suica on Garmin Pay.

Taken together I think there is a better chance Google will go deep instead of cheap, hopefully sooner than later. Google Pay Suica and Google Pay PASMO on Pixel and Fitbit devices from anywhere would be a very welcome development.

Update: Not labeled on diagram

Pixel 5 was announced and FeliCa support is still limited to JP models, more cheap instead of deep. Pixel support pages (screenshots) list FeliCa support in the ‘Not labeled on diagram’ section with Osaifu Keitai links and this new bit: “To use FeliCa on Pixel 4 and later Pixel phones you’ll need 4 apps that should automatically open during setup.” This is the enablement step that Google blocks on non-JP Pixel models. The strange thing is that Mobile FeliCa is hiding in plain sight on all Pixel models, if Google wanted to they could allow enablement remotely.

This confirms the FeliCa situation won’t change for Pixel until Google builds their own Google Pay replacement for Osaifu Keitai software instead of candy wrapping it. It all comes down to what Google wants to do regarding Suica support on Fitbit. Something will have to change in Google Pay if they want to do that.

Special warning to Hong Kong Octopus users: don’t buy a Pixel device for using the Octopus Mobile SIM. FeliCa Dude reported that Google purposely crippled Pixel 4 SWP support for products like Octopus Mobile SIM and this is the case for Pixel 5 as well. Only use officially supported devices for Octopus Mobile SIM.