5 ms·
This seems like a positive developmental, though still a bit like a one-sided negotiation. In HN's thoughts, how should Google have approached this? (I do not
by tomrod 8y ago
This seems like a positive developmental, though still a bit like a one-sided negotiation.
In HN's thoughts, how should Google have approached this?
(I do not work with or for Google in any capacity).
- rswail 8y agoLike a car company with a 7 year warranty, with a guarantee of support for parts for the life of the house. Google have a responsibility to their customers. In this case, the customers are the people that actually buy the hardware. It's not "Temperature As A Service".
- cube00 8y agoOr Nexus phones, completely turned their back on security updates after three years while the hardware is still working.
- eitally 8y agoFWIW, Philips just did something even worse with their Hue system, essentially forcing "legacy" (v1) Hue customers to spend $50 to buy a v2 Bridge if they wanted the system to keep working as usual. Coincidentally, this was a few years after they backpedaled on a decision to disallow control of non-Hue bulbs (https://www.home-assistant.io/blog/2015/12/12/philips-hue-blocks-3rd-party-bulbs/ https://www.home-assistant.io/blog/2015/12/12/philips-hue-bl...) after public outcry.
- nitrogen 8y agoI haven't used a v2 bridge, but v1 bridge I have is horribly slow and underpowered. I'm more annoyed by the API changes they've made over time that broke my integration with the bridge. At least there is a local LAN integration option though, and you aren't forced to integrate with a remote service that might be shut down unexpectedly.
- alttab 8y agoI think Google just realized the path they were taking was too short. They underestimated the nest contingent which is funny considering how much data they collect. It seems like product management and engineering wanted to do it quickly and didn't do enough customer homework. Then they had to backtrack, still sounding like douches because of their "if we change our minds we will keep you informed" tidbit. I'm genuinely curious about their Alexa support through the transition. Seems they are willing to give away customers who want nest and nothing else.
- shakna 8y ago> For these custom integrations, partners will undergo security audits and we’ll control what data is shared and how it can be used. It sounds like they're going to keep a tight control of their relationship with Amazon on this one - I imagine the negotiations are going to be extremely tedious.
- mikeash 8y agoThey should keep the old API working.
- josteink 8y ago> In HN's thoughts, how should Google have approached this? Google/Nest created an API for developers to use with an associated slogan to for marketing if end-user devices which people buy with a 10+ year plan of ownership because it’s built into their bloody homes. That obligates Google to keep this stuff working for 10+ years, as is, no weasel words. No exceptions. Anything else is a scam. Edit: looking at Google’s history they clearly don’t have the intention nor ability to do this. Im not buying anything Nest/Google Assistant ever. I’m not interested in time-bombed devices.