[harles]

That’s a pretty uncharitable take. Given the scale of their recent launches and amount of compute to make them work, it seems incredibly smooth. Edge cases always arise, and all the company/teams can really do is be responsive - which is exactly why I see happening.

[tracker1]

A company with a literal embedded payment processor, including subscription services for half of all mobile users can't manage to take payments for their own public facing services seems like a huge fucking failure to me.

Especially for software developer and tech influencer focused markets.

[lazide]

It’s a sign that getting the product out took priority over getting paid for it.

Take that how you will.

[tracker1]

Considering the product itself seems to be excessively limited without actually getting paid for it, and the paid tier itself having so many onboarding issues, as a critical usage path, it's pretty bad.

This is in a $3.6 Trillion company, for a product they're spending billions a quarter to develop, with specialized employees making mid 6-figure to 7-figure salaries and bonuses... you'd think somebody has the right connections into the departments that typically handle the payment systems.

My expectations shoot up dramatically for organizations that have all the funding they need to create something "insanely great" in terms of user experience the further they fall short... I don't know who the head of this group/project/department/product is... but someone failed at their job, and got payed excessively for this poor execution.

[recursive]

Why should the scale of their recent launches be a given? Who is requiring this release schedule?

[rishabhaiover]

the market

[recursive]

If it's a strategic decision, then its impacts should be weighed in full. Not just the positives.

[windexh8er]

We're talking about Google right? You think they need a level of charity for a launch? I've read it all at this point.