Hacker News Reader

Comment by brickfaced | Hacker News Reader

>Sundar doesn't say, we need more XR.

Right, that's the job of some random PM who will launch a half-baked XR project that overlaps with a nearly identical XR project down the hall, which will compete with its fellow Google project/product in the marketplace and confuse customers before getting killed within 18 months of launch. See also Google Wallet and Google Wallet (yes), Allo and Duo and GChat and Hangouts, and so on.

View on HN

> See also Google Wallet and Google Wallet (yes)

... wat? Are you suggesting Google has two different services both called Google wallet?

Correct. Google’s forays into payments, including identically named but different products, is so complex that it has a Wikipedia diagram:

https://en.wikipedia.org/wiki/Template:Google_payment_apps

Oh sweet baby Jesus what the fuck.

Not one, not two, but three different things called Google wallet, and four different things called Google Pay, one of which was formerly called Google wallet and one of which went on to be called Google wallet.

How is this real?

Well this explains why every time I get payment autofill suggestions from Google it's a random one of four or five possible auth flows, and pulls from an arbitrary one of at least two separate data sources with different sets of cards saved...

I let my password manager handle it now.

That is genuinely jaw-dropping.

Wait till you see Google Jaw and then witness Google drop it.

To be fair to them, the diagram makes it look worse than it actually was. From the user perspective, you got your Google Wallet app replaced by a Google Pay app which got replaced by a Google Wallet app. They all work the same (the last one has an extra tab for transit cards), had the same data/information (loyalty and bank cards), and even look pretty similar.

Yeah, it was dumb having your app change names and slightly looks, but materially, little changed.

Reply on news.ycombinator.com