Its not a new problem though, and its not just billing. The UI across Gemini just generally sucks (across AI Studio and the chat interfaces) and there's lots of annoying failure cases where Gemini will just timeout and stop working entirely midrequest.
Been like this for quite a while, well before Gemini 3.
So far I continue to put up with it because I find the model to be the best commercial option for my usage, but its amazing how bad modern Google is at just basic web app UX and infrastructure when they were the gold standard for such for like, arguably decades prior.
We are talking here about the most basic things- nothing AI related. Basic billing. The fact that it is not working says a lot about the future of the product and company culture in general (obviously they are not product-oriented)
My first thought was this is the whole thing about managers at Google trying to get employees under other managers fired and their own reports promoted -- but it feels too similar to how fucked up all the account and billing stuff is at Microsoft. This is what happens when you try to "fix" something by layering on more complexity and exceptions.
From past experience, the advertising side of the business was very clear with accounts and billing. GCP was a whole other story. The entire thing was poorly designed, very confusing, a total mess. You really needed some justification to be using it over almost everything else (like some Google service which had to go through GCP.) It's kind of like an anti-sales team where you buy one thing because you have to and know you never want to touch anything from the brand ever again.
No one should even notice the payment flow. This isn't Stripe where the polish on the payment experience is a selling point for the service. At Google, paying for something should be a boring but quick process that works and then gets out of the way.
It doesn't need to be good. It just need to be not broken.
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.
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.
But then we'd complain about Google being a slow moving dinosaur.
"Move fast and break things" cuts both ways !
(ex-Google tech lead, who took down the Google.com homepage... twice!)
Its not a new problem though, and its not just billing. The UI across Gemini just generally sucks (across AI Studio and the chat interfaces) and there's lots of annoying failure cases where Gemini will just timeout and stop working entirely midrequest.
Been like this for quite a while, well before Gemini 3.
So far I continue to put up with it because I find the model to be the best commercial option for my usage, but its amazing how bad modern Google is at just basic web app UX and infrastructure when they were the gold standard for such for like, arguably decades prior.
[dead]
We are talking here about the most basic things- nothing AI related. Basic billing. The fact that it is not working says a lot about the future of the product and company culture in general (obviously they are not product-oriented)
My first thought was this is the whole thing about managers at Google trying to get employees under other managers fired and their own reports promoted -- but it feels too similar to how fucked up all the account and billing stuff is at Microsoft. This is what happens when you try to "fix" something by layering on more complexity and exceptions.
From past experience, the advertising side of the business was very clear with accounts and billing. GCP was a whole other story. The entire thing was poorly designed, very confusing, a total mess. You really needed some justification to be using it over almost everything else (like some Google service which had to go through GCP.) It's kind of like an anti-sales team where you buy one thing because you have to and know you never want to touch anything from the brand ever again.
There’s nothing basic about billing.
4 replies →
this way is better. Burn in public, burn much faster.
Imagining the counterfactual (“typical, the most polished part of this service is the payment screen!”), it seems hard to win here.
No one should even notice the payment flow. This isn't Stripe where the polish on the payment experience is a selling point for the service. At Google, paying for something should be a boring but quick process that works and then gets out of the way.
It doesn't need to be good. It just need to be not broken.
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.
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.
It’s a sign that getting the product out took priority over getting paid for it.
Take that how you will.
1 reply →
Why should the scale of their recent launches be a given? Who is requiring this release schedule?
the market
1 reply →
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.