It will be different this time, they said.
It will be different this time, they said.
These customers are different, Google had to go through a lot of work to allow them to legally use their products, and will get to charge a premium. This is the high end of B2B, and unless they're moronic (which is possible) they'll know the medical industry moves slow, so any customers they acquire will almost guaranteed be long term customers.
..." while our engineering teams have put a lot of effort and dedication into building Google+ over the years, it has not achieved broad consumer or adoption, and has seen limited user interaction ...""""
I'm skeptical too, we can only wait and see. I'm essentially just hoping they understood the market they're entering but hey it's Google.
I'd also imagine they'd have service contracts for X years though? I can't imagine a health network wanting to use their service without guaranteed support for 5/10+ years. (Heck I imagine it'd take a year or two to even develop applications that use it)
https://techcrunch.com/2011/06/24/google-shuts-down-medical-...
My experience with Azure and AWS paid support frankly isn't much better. But Google is definitely the leader in absolutely horrible paid customer service.
"All you need to do is rewrite your software to use a different solution"
You do understand why this isn't an OK answer to a lot of people, right?
It appears to be more (5) steps than changing a key.
For me, Google has clearly demonstrated that I should not use any of its services until several big movers are on board.
Apple has had consumer-facing health software for longer than Google at this point: https://en.wikipedia.org/wiki/Health_(Apple)
And, since this is still Beta, it's excluded from the Google Cloud Deprecation policy at https://cloud.google.com/terms/deprecation. (And even if it was covered, you'd only have one year to migrate off of it -- so I hope you don't have a FDA-certified hardware widget directly talking to Google's APIs).
> And, since this is still Beta, it's excluded from the Google Cloud Deprecation policy
Well, sure.
> And even if it was covered, you'd only have one year to migrate off of it -- so I hope you don't have a FDA-certified hardware widget directly talking to Google's API
Yes, that would be very bad design. And not just because of the deprecation policy.