It's good they're providing refunds, but the decision to shut down whatever service the glasses relied on in an excellent way to demonstrate "When you buy a product from us, you can't trust that it's going for any given period of time, and we'll just brick it when we get bored of it".
Google of course is famous for doing this with many of its products, but in the long run this type of behavior can make it harder for startups to introduce new products/services. Some customers will ask the question "So what happens when you get acqui-hired in a year and your parent company decides to shut down your service either immediately, or a year after they tell customers that everything will continue unchanged?"
Of course the bigger lesson here is don't buy products which rely on a third-party service to function.
People didn't buy the product from Google. They bought it from North -- which was later acquired by Google for less than they had raised as they were apparently running out of money [1]. If North had not been acquired and had simply gone out of business, the service also would have been shut down (and likely without a refund).
"for less than they had raised" - that's actually not true and sloppy journalism from the journalists that wrote it.
If you look at North's funding - the difference between the suspected purchase price of $180M and what they raised ($200M) is a $24M loan they received from the government of Canada [1], which was called back shortly after (because of layoffs) [2].
The remaining $4M difference is probably interest on a standard debt financing loan of $40M they received [3] and some rounding error in the $180M suspected purchase price.
It seems Google bought them for the exact amount raised, in both debt and funding.
Sorry for the quibble, but it's only a win in Vegas because the expected value in Vegas is negative due to the house edge. The expected value of human effort is typically positive, so a push is not a win in the development of companies.
The expected value in tech startup investment is also negative, I'd suggest. Just like Vegas, all the rational players are really just gambling on the 100x jackpots, and all the "dreamers" who believe and double/triple down on their ideas that never make a profit - fund the whole game.
> The expected value in tech startup investment is also negative, I'd suggest. Just like Vegas, all the rational players are really just gambling on the 100x jackpots
Expected value is precisely the quantity that says that the value of a 3% chance of 100x returns is a 3x return. Also, how can you say that the expected value of investment is negative, but that the rational players are gambling at all? Perhaps you mean that the 3% chance of 100x (or whatever) is irrational for the founders, which may be true, but that isn't really what your words say.
Sure, but "3% chance of 100x returns" is firmly in "dreamer" territory. Best guess I can find is that it's at least an order of magnitude smaller than that:
A 0.3% chance of a 100x return is a 70% loss. (And over 10 years, a 3x "return" is pretty much just breaking even anyway)
The "rational players" in this game are the VCs who're raking 2%/year from the investors in their funds (whether they succeed or not), and also skimming their 20% liquidity event bonus - so they benefit from the winning funds without ever having any personal financial risk in all the losing funds.
In my opinion, pretty much every other tech startup investor could be categorised as one or more of 1) Dreamers (who genuinely believe _this_ one is going be "their unicorn!!!"), 2) Lottery players (throwing away a hopefully insignificant enough amount of money to them, in return for the entertainment of maybe winning big one day) 3) Horse race gamblers (someone who believes they're better informed than 99% of the other investors in their chosen horse/jockey/startup/founder) 4) early stage employees who wittingly or unwittingly accepted vesting options as part of their renumeration (these are arguably somewhere on the spectrum between #1 and #2) or possibly 5) insider traders (pretty much a legally actionable case of #3).
(And I say this with the hindsight of having been the first four of those - some of them several times over...)
From what I've been told they didn't. Only the founders managed to get anything out of the sales, plus took pretty lavish salaries while the company was operating (a lot of it from government subsidies).
Given that analogy, I'm curious how a VC would view this kind of exit. Is breaking "even" seen as some kind of success given the higher failure rate for venture backed companies?
A friend of mine was CTO as a startup that raised like $100 million. They knew it was gonna flop after a while, and wanted to wind the company down and return 50% of the VC’s money. The VC told them to take extreme risk and/or drive the company into the ground before returning the cash. A 100% loss was expected, but a 50% loss was somehow an embarrassment.
Pretty sure PG has talked about this and said something to the effect that all of their money is made on the extreme outliers rather than the ordinary failures or modest successes. Knowing that, it kinda makes sense that they'd rather see the startup push and try to go big rather than just going home.
Well, it depends on the numbers involved. If they estimated a 5% chance of getting $2 billion, then that would be a 2x expected return on a $50 million cost, which is entirely rational for investors with huge pockets. But if they estimated a 1% chance of getting $2 billion, then that's a 0.4x expected return (an expected loss of $30 million), which is irrational, unless the "embarrassment" is a significant factor for the VCs, and that would be interesting.
Yes, that's a fair point--the numbers for the potential upside and downside matter a lot here. I was only trying to make the case that in some cases, the downside risk may not hold a candle to the potential upside.
I also think that they want to see founders who are willing to charge up those hills rather than to shirk away from challenges that seem to be too big for them. Sort of like burning your ships behind you in terms of morale--if it's go big or go home and you can't go home, there's only one choice left.
Supposedly for a VC it is a bit better to liquidate at break even than to limp along with an uncertain future, because VCs no longer have to spend time going to board meetings.
Stories like this are why I will never buy a product like Stadia from Google. There is zero guarantee the product and games purchased on the platform will be usable next month (exaggerating a bit) or next year.
This extends to all things Google. When building a new product, I push hard to use any alternative to Google because the future of their products is so uncertain. Sure, there are a few Google products that can be reasonably relied upon, but that list is small.
Ever since Google told me to buzz off when I contacted them about the bootloop of death that bricked my Nexus 6P immediately after an automatic software update, I haven't bought a single hardware product marketed by them or supported by them. I won't even let myself use Google Fi. They earned my distrust.
I think one big thing that differs between the Nexus line and the Pixel line of phones is who was actually supporting the phone after its sale. The Nexus phones were these shared branding between Google and the makers (LG, HTC, whoever). So it led to some pointing at the other person when there were problems.
With the Pixel line, Google fully owns support of the devices, which makes it a bit easier for Google to deal with customer support issues like this.
Ah yes the famed google customer support. Spent five days trying to get a g-suite dashboard error fixed immediately after provisioning. Eventually I switched to O365 with no regrets. And then there was the bricked chromecast from hell which they wouldn’t even acknowledge. Switched to Apple TV with no regrets.
Add the usual quality control (how many years did my android phone alarm not go off or my SD card get trashed with photos on). Nope!
I don’t accept this line of reasoning but appreciate you sticking up for your employer.
I’ve noticed this tactic more and more. Price a product as if it’s yours, but then disown it when inconvenient.
I can’t imagine Apple saying something like “that’s a Samsung issue, take it up with them” because of a component.
As a customer, I don’t want to have a decoder ring for how to get support for my product. If it says google and is sold by google then google should fix it. Maybe they sub it out to HTC or Huawei or whatever, but don’t make me know about it.
If google makes bad supply chain decisions then own up to it. Not doing so just makes Google seem incompetent at management as I don’t care or have any value in them directly for manufacturing.
> As a customer, I don’t want to have a decoder ring for how to get support for my product.
As an Australian this is so weird to hear. I have a business relationship with the person I gave money to, not some third party factory or manufacturer that I never met. The law requires the merchant to take the return and make it right, after that it's their problem. Most likely they have a better idea about the next step than I would as a random customer.
It's not a US thing, it's mainly a Google thing. They appear to have decided that they can reduce costs by saying "it's not our problem" in response to customer complaints about defective products. They do this for defects that may not even be rooted in the hardware itself.
My general impression is that most companies are quick to take responsibility for consumer products sold in the US, unless product failure results in liability for a major safety risk (think McDonald's coffee scalds or Ford Explorer rollover accidents).
If the engine computer fails in a BMW due to a widespread defect, the BMW dealer doesn't send the customer to Bosch on a wild goose chase. If a Macbook Pro SSD fails due to a widespread defect, Apple doesn't tell the customer to call Samsung. They either take ownership of the problem and make the customer happy (with the expectation that a brand-loyal customer's next purchase will pay the cost of solving the current problem), or they make an effort to offer some kind of solution at the customer's cost.
I think I'm talking about something a little different, which is my mistake. The parent was discussing a manufacturer disowning components within items, as you noted.
I'm taking it a step further and saying we don't even talk to the manufacturer, just the store - it doesn't matter what Apple thinks (unless you bought it directly from them). There's a legal concept of whether or not the item is fit for purpose or defective (generally, if you knew X would happen before you bought it, would you still have bought it?) which shuts down excuses.
That's funny, when I bought my Nexus 4 I don't remember the front of the box saying, "Nexus 4: A shared branding between Google and LG." It said "Nexus 4" and had Google's logo displayed somewhere on there. I bought it from store.google.com, my credit card was charged by Google. It said "Google" on the box, so if I had an issue with it I would have expected Google to fix it. Anything less and they'd have been in the wrong.
I get what you're saying, I understand it. But from the consumer's point of view it just doesn't matter. The nature of the business relationship between Google and whomever should not be their concern. It rings of the same cop-out Amazon likes to make, that I'm not dealing with them, I'm dealing with a some third part merchant even though I visited Amazon.com, I paid Amazon, and the item is shipped to me by Amazon. They want to you deal with their suppliers.
My Pixel broke suddenly after an update. Android debugger console clearly showing a spew of ALSA errors. Hundreds of other people having the issue on forums - been 3 years and no patch has resolved it. I hang onto the phone as a cautionary tale not to purchase anything from google... Have never been able to get a customer rep on the line who can say anything other than "sorry, cant help". No refunds, no RMA, nothing. So... What customer support are you referring to?
If it was an open platform, I'd fix the issues myself. If it was a closed platform, I'd get it replaced. Google fails at being non-Apple and also fails at being Apple.
This also happened with many people's Nexus Players, a Roku/Firestick competitor, myself included. It's co-developed by both Google and Asus. Of course after the update bricked them Google tried to blame Asus and put it on their shoulders to provide a fix and Asus seemed to do the same. Needless to say, I won't buy Google products anymore.
dear googler. fyi -this is what that thinking and lack of integrity and support does:
you have gcp. working for vars over the years, per year i sell over $10mil of solutions that run or dr to cloud. i have not once put gcp as an option in front of a customer - all azure or aws. google has, and will, lose millions in gcp revenue. because of me. and this is true for most vars.
now, as far as others in my office -8 people like me. only one puts gcp in proposals. he's new.
this is very common. we don't trust or respect your offerings -too flaky, not going to risk our customer relationship when you drop the ball and we get the hit for proposing a bad solution. and yours are all bad solutions. not because of function -because it's risky for a business to be involved with you in any way, or count on you for anything.
you probably lose 50-80mil annually from my office alone. and it's not just lost cash. it goes to your direct competitors.
and i don't know a single person who wants you to fix your practices and act like a real company. only 2 real cloud players drives up prices, and we get more on our spiffs.
and last i checked, aws and azure have been, are, and will always be kicking your ass. because even if you fix your business practices now, you'll have to wait 30 years before all the sales staff and company decision makers retire. and that is eternity in tech time.
That's a poor (and partially false) defense for Google's handling of the Bootloop of Death, for the following reasons:
I bought Google's flagship handset online from the Google Store. It was branded as the "Google Nexus 6P", it was shipped to me by Google, and it bricked itself while booting after a Google-supplied Android update. Google provided and managed the warranty. I had one warranty claim with them prior to my phone bricking itself, handled entirely by Google; Huawei was not involved in that claim at all.
My relationship as a consumer of a Google product is with Google, not with its contract manufacturer.
The Bootloop of Death affected multiple SKUs across different Nexus models. The 5X was manufactured by LG for Google, and the 6P was manufactured by Huawei for Google. The Bootloop of Death was present on both models.
If Google has a quarrel with Huawei, LG, or another contract manufacturer over the cost of managing a defect, that's their prerogative. However, I am not party to that quarrel. I am just a customer who bought Google's flagship handset.
Google suggested that I contact the nearest Huawei service center...in mainland China. The company took an arrogant "who, me?" attitude toward its flagship handset, and tried to weasel its way out of dealing with valid customer complaints, rather than taking some semblance of responsibility for an obvious problem.
> The Nexus phones were these shared branding between Google and the makers (LG, HTC, whoever)
This is not true. The Nexus 6P was marketed by Google, not in a shared manner. You're thinking of the Nexus 6, a Motorola-made device that preceded the 6P and was offered in some markets without Google branding.
> With the Pixel line, Google fully owns support of the devices, which makes it a bit easier for Google to deal with customer support issues like this.
Google fully owned support for the Nexus 6P until the bootloop issue came around, at which point Google changed its policies. Also, Pixel devices have been manufactured by competing handset manufacturers for Google (Pixel 2 phones were manufactured by HTC and LG).
The result of my experience is that I will never, so long as I live, ever buy another Google hardware product. Not a single one. I will not buy a Nest Thermostat. I will not buy a Chromecast. If my best friend has a lapse in judgment and makes the mistake of buying a Pixelbook, I will wait for him to leave it on the couch, unintentionally sit on it, and buy him a 16" Macbook Pro as a replacement -- apologizing profusely all the while, unlike Google support which was ostensibly trained not to use the phrase, "I'm sorry." Every time someone tries to defend Google for its handling of the Nexus Bootloop of Death fiasco, I add twenty years to the length of time that the trustees of my estate will prohibit my assets from being used to buy Google hardware products after I am dead and gone.
Modern poetry, as someone who got a Nexus 5X that boot-looped after 13 months (just enough so my carrier would say "asks the manufacturer") I wholeheartedly agree with your take. It was a pathetic demonstration of the subpar capabilities of Google to deal with actual paying customer and it makes me angry to this day.
> If my best friend has a lapse in judgment and makes the mistake of buying a Pixelbook, I will wait for him to leave it on the couch, unintentionally sit on it, and buy him a 16" Macbook Pro as a replacement -- apologizing profusely all the while
Ahh yes, the wonderful Google support team. Spend any time looking at /r/GooglePixel, or doing searches on twitter, and you'll realise that isn't an improvement at all.
When the Pixel works, it works great. If you ever have a problem though, good luck. You're in for a nightmare.
I'm really disappointed with my pixel phone. The camera is partially stuffed up (seems to be a misaligned lens causing the image to be blurry) The battery life is really poor, and the usb port is loose.
These are all things I would be fine replacing myself but it seems that everyone who has tried this ends up cracking the display since the phone is glued together. Google also does not sell replacement cameras so you have to find one second hand which isn't easy or cheap.
I will never buy another google phone but I'm not really sure what my options are.
For the price of that phone I could buy 50 second hand android phones that would work much better. I also haven't seen any evidence that purism will be selling replacement parts or that parts will be available in 3+ years when they are needed.
Well I would hope so, considering Pixel phones cost double or triple what Nexus phones did.
I remember when Google bought Revolv and then stabbed all their customers in the back by bricking all their home automation and then graciously offering them a discount on a new Nest home system.
Google would remotely brick pacemakers if they stood to make money off doing so and anyone who thinks they can be relied upon long term is a bloody fool.
I'd argue Google doesn't support them at all. They don't have repair centres, they don't sell parts - if I break a screen in my OnePlus, I can send it back to OnePlus and have it replaced with a genuine part for £79 last time I checked. With Google I know someone who cracked the screen in the Pixel 4 and Google's response to it was "well, sucks to be you, we don't repair any phones at all". That's shocking, and unacceptable for any hardware product.
that's cute. 2011 you say? you can run android 10 (current latest release) on galaxy s2. released in 2011. and it's actually usable, because screencandy has been removed to give it a perf boost. can you run ios 13.6 on your 2011 iphone 4s?
i know in the iphone world it's important how long apple updates it. in the android world that doesn't apply. the manufacturer doesn't have to. because literally anyone can, and does.
> in the android world that doesn't apply. the manufacturer doesn't have to. because literally anyone can, and does.
I have two problems with this model. The first is that it really only applies to the kind of people who would be in this thread on HN - consumers at large are not updating their phones based on some community-supported Android rom.
The second is this: do we really want to train non-technical people that it's ok to let random organizations on The Internet control the operating system on their phones? These are deeply personal devices that can be relatively trivially turned into 24/7 remote surveillance stations, and say what you will about open source but with rare exception these roms are not undergoing line-by-line code audits.
In my opinion, the world is better served when companies support their own hardware.
If it turns out that Apple is spying on users, we have legal recourse. If orchiddroid928 on GitHub is doing it, that's a different ballgame.
linux is community supported. just like you can get linux from redhat, you can get your android rom from large companies. lineageos is a popular one.
i won't argue with the rest of that, as you are arguing open source is inferior. one you convince every enterprise out there not to use open source, you can revisit this with me.
you are also arguing all servers and consumer pcs should be made by microsoft, since they run windows.
I don't know what Linux has to do with this and I won't litigate the open source dogma, but on this point:
> you are also arguing all servers and consumer pcs should be made by microsoft, since they run windows.
That's not really what I'm saying at all; this isn't like e.g. expecting to get Windows updates through Dell, it's more like expecting that Dell will continue to deliver compatible drivers for their hardware that enable the updates I get from Microsoft to keep working.
That's a basic expectation when we buy PC hardware, in part thanks to the relative standardization of PC components - if I couldn't update Windows ~2 years after I bought a laptop and Dell's answer was "maybe someone in the community can help you", I'd be incensed.
In the smartphone/tablet market, that's just business as usual.
The only reason that PC hardware is standardized is because MS and Intel came up with standards in 1995 and continue to update them along with other committees.
Dell doesn’t have to release new drivers. I installed Windows 10 on a Dell E6500 Core 2 Duo 2.66Ghz laptop that was sold in 2009.
My mom still occasionally uses my Mac Mini Core Duo 1.66Ghz from 2006 with Windows 7. This was without any drivers from Apple. Windows 7 recognized everything.
Going even further back, I bought a DX/2-66 DOS Compatibility Card from Apple in 1994 that came with Windows 3.1. I upgraded it to Windows 95.
Microsoft figured out how to nourish a platform over 25 years ago. Google and Android - not so much.
you update drivers on your phone? i just flash a new rom. it's got all the drivers i need in it. and on a phone from 2011, i can put the latest operating system. you cannot. you then spout the superior glory of being stuck on an outdated version because you got a security patch. how is that superior to also security patches, and even latest os if you want?
you don't need anything from dell to update windows. you literally just install windows.
the reason i bring up linux isn't clear? because android runs on it.
a normal person downloads a recovery app and the rom, and uses the app to flash any rom they want. what you're saying is you'd rather get your windows updates from lenovo. software and hardware are different things.
I’m all in on Apple phone-wise due to having too many Androids die on me in one year but the point about 3rd parties supporting some old hardware is very true. I have an ancient Barnes & Noble Nook tablet that I flashed with a custom rom and the thing is really snappy and responsive. The battery holds a charge and everything it’s really surprising.
can your mom upgrade windows 7 to windows 10 without you helping her?
i actually do know what's in the rom. and so does. anyone else who wants to check. and you have hundreds of 3rd party people who do. source code is available. you're literally arguing hardware and software should be tied together to the hardware manufacturer. the entire world of computers disagrees.
>can your mom upgrade windows 7 to windows 10 without you helping her?
Quite possibly, yes! I recall Microsoft pushed upgraded to Windows 10 quite aggressively at the beginning to the point it basically scheduled automatic upgrade. That was 5 years ago, I might not recall correctly.
The big difference between iOS/Windows 10 upgrades and installing custom ROM is that in the iOS/Windows 10 case, you click one button (or even let it install automatically!) and it installs itself. It cannot be easier probably. I can expect it was reasonably tested and that it's reasonably safe.
With custom roms, it really needs to be your hobby to do that. For majority of people, it's not viable solution to do that - they lack time and/or knowledge.
Putting Android 10 into Samsung Galaxy S2 is kinda like putting Corvette V8 engine into VW Beetle. It's possible, there are people that did it, but it requires skill and time to do that.
We probably have (at least in part) Apple’s iOS enterprise success to thank for this. No procurement manager is going to sign off on a fleet deal for 10,000 phones without some long-term support assurances.
Google seems completely uninterested in servicing that market with hardware. They could’ve absolutely dominated e.g. aerospace MRO with Glass + pixel tablets but instead most companies are just building iPad apps.
Had Google been serious about the Nexus it would have made contracts that would legally bind those maker to how many years Google would see fit, and they would have to provide such support or pay compensation when not.
Google excuses only work for those that don't understand law.
Google fiber support is terrible too. There is no way to transfer service to another address. Instead you have to sign up with a different Google account at the new address.
Absolutely. The fact that they choose to not provide this guarantee is a major red flag and a strong reason for me to not spend money on that platform. On the other hand, I have zero concern that my digital licenses of XBox or PlayStation games will vanish within the next couple decades.
Well, you should have a little concern. On my switch, I can buy games either digitally or physically for just about the same price. I buy most games physically, as one cannot guarantee the server that downloads games will work in 10 years (my Wii doesn't do this type of stuff now, but its less integral).
Pretty much any online game will be shut down, its just a case of when.
> as one cannot guarantee the server that downloads games will work in 10 years
While true, the pain point with Stadia is you have no downloads, for better and for worse. If Nintendo take their download servers down, you can still play all of your downloaded purchases.
On that note, I have much more faith in Nintendo's future handling of digital purchases this time around. They've put a lot more effort into the Switch's digital services compared to the Wii, which at times felt like an afterthought with the whole "WiiWare" artificial gatekeeping fiasco.
I'm a big fan of Stadia but really can't argue against this thought process. It would be nice if Google had some way of marking products that were potentially going to be cancelled vs those that have passed the threshold and will not go away unless Google is in danger of going away completely.
Reader really looks like the breaking of a dam in hindsight.
If Stadia were just a monthly subscription and you could play all the games, it wouldn't be hard to swallow because they just stop charging you when the service goes down and you got your value out of it while you had it.
It's the "purchasing" of the digital good that's the problem because you loose access to something that you think you "own" when in fact it's more of a lease.
There wasn’t any confusion. Their point was they’d much rather pay a monthly fee, because as it is, paying full price to “own” a Stadia game is ridiculous because Stadia is going to end up dead like most other google services and all the games you “own” will likely disappear.
The problem is that Valve doesn't have a history of just cancelling their products and shutting their customers out. Google does, and an extensive one. So when they offer a service where you can buy software and said software will only work for as long as Stadia is around, I don't trust Google that service will exist in 3 years. And once it finally dies what will Google do? Give everyone AdWord vouchers?
Those 3 along with maps, ads, and a handful of others make up the list of "safe" Google products.
I agree with you though, it is the niche products that get shutdown. My point is that being an early adopter of Google products is a very risky move. Until a product is adopted by the masses and profitable, it should not be considered safe.
Back in the day, I used to be all in on the Google bandwagon. I was in on Wave, Buzz, Meebo and bunch of others. After a few years of cycling through the standard phases:
1) Wow this is really cool
2) Wow I'm starting to use this everyday
3) Wow my friends should know about
4) Google is killing this
Once you get over the idea their killing something you started to rely on and then you experience their "customer service" a few times you just wonder if its actually about trying to make the world a better place, or just adding revenue to their bottom line.
My conclusion a long time ago was not to use them for anything personal and FFS nothing I would have my business rely on.
Several years later, Wave was especially disappointing to me: It was Slack, before Slack was a thing. They just didn't know how to market Wave, so no one knew why it was useful.
If Wave was first released a couple years later, with identical functionality, I think it would've done well.
The same problem applies though. It's not just services disappearing, it's the complete lack of support for services.
I'm in the process of moving everything off of my gmail email as I have a friend that recently lost access to their gmail account. There was no way for them to get it back – no human to speak with, no steps that they could follow to recover their account. They were supposed to be able to "sign in with an old device", but that didn't work either. Just gone. And apparently this has happened to a lot of people.
The founders are not joining Google and from what I heard employees were not even offered interviews, despite the announcement that the company was going to join their offshore location in Canada. It's a pure patent play, acquiring the Vaunt patents from Intel.
Every product relies on an external ecosystem for it to be useful. The lesson is to that if you're buying a product that isn't already highly successful, don't get too attached. Incidentally, the vast majority of the world already learned this lesson, it's the reason why most people aren't early adopters, nobody ever got fired for buying IBM, etc.
Once an android phone stops receiving updates, its only a matter of time until google play services stops working on that version of android, and then it becomes a big PITA to do anything google related with it, as it keeps redirecting away from web pages you to apps that tell you that you can't use them.
I wouldn't rely on Android to not go anywhere.
The new Android version might have introduced features that render that old app worthless.
Examples of such changes.
Locking down use of private APIs (abused by some apps), locking down NDK to the official Android native APIs and public shared objects, both cases app gets killed when doing naughty stuff, sandboxed file system (now really enforced in upcoming 11), permissions (now enforced with the Play Store minimum target version), and a couple more.
So if the app happens not to be constantly updated, it might just be rendered worthless with a new Android phone.
Not just Google buy any company's cloud-connected product.
I have a Roomba i7, and it works well, but it's 100% reliant on a web connection to control and to train it's automapping feature.
If iRobot gets bored with the model and decides to discontinue it and the cloud host, am I going to be stuck with an expensive paperweight, even it's mechanically still in great condition?
In an ideal world, Google could keep all the endpoints up and functioning. The issue is as software ages, exploits turn up and you end up requiring a team to just maintain a service with no future.
> Some customers will ask the question "So what happens when you get acqui-hired in a year and your parent company decides to shut down your service either immediately, or a year after they tell customers that everything will continue unchanged?"
An acquihire is not the most likely outcome. The most likely outcome is that the startup will fail, possibly pulling support for the product with no advance notice.
An acquihire or acquisition is one of the best chances customers have for continued support, unless the startup manages to go public and survive on its own.
Google of course is famous for doing this with many of its products, but in the long run this type of behavior can make it harder for startups to introduce new products/services. Some customers will ask the question "So what happens when you get acqui-hired in a year and your parent company decides to shut down your service either immediately, or a year after they tell customers that everything will continue unchanged?"
Of course the bigger lesson here is don't buy products which rely on a third-party service to function.