Earlier quoted context omitted.
If you build on someone else's platform, the best case is you get to be a sharecropper and can make money as long as you don't make so much that your platform-betters get jealous. The more typical case is this, where you get to spend your time and money doing real-world R&D and discovery of what works for them, for free. If you're going to dance with a vampire, don't be surprised when it bites you.
One way or the other aren't most of us building for someone else's platform anyway?. Mobile, desktop, browser...
Google Is Turning Off the Works-with-Nest API
441–450 of 600 posts
Re: Google Is Turning Off the Works-with-Nest API
#442Earlier quoted context omitted.
I agree. I used to be a fan. They were explicitly not evil, gave lots of open source stuff away for free, made lots of other free services. Turns out they were just making us dependent on them, and now that they've got us, they do whatever they want. We need to make ourselves less dependent on Google. Move away from GMail, use Firefox, DuckDuckGo, OSM, federated social networks, etc. I don't have a good replacement f…
... use the contact pages on web sites you like that use AMP- to stop using AMP.
Re: Google Is Turning Off the Works-with-Nest API
#443Earlier quoted context omitted.
The month Google originally bought Nest, I sold my thermostat to someone else and picked up an Insteon thermostat instead. My Insteon thermostat's been a reliable partner since, and doesn't send my data to anyone. I actually turned a profit on it, since I got rebate credit from my electric company originally for buying it.
I'm really happy with the Ecobee as well. The Alexa integration in the newer model doesn't work well possibly due to inferior microphones, in my experience, but I didn't want that anyway so it fits my needs perfectly. In a few years, it will also return a profit due to an at-purchase and annual credit that my electricity utility provides.
Re: Google Is Turning Off the Works-with-Nest API
#444This seems to include all of us using them in open-source "hobbyist" environments, like Home Assistant and Node-Red. I'm quite frustrated by this; I'll never buy another Nest product again, and I now regret my purchase of the Nest Thermostat. All the rest of my IoT stuff is either open-source hardware/software, or at the least local-only with known protocol interfaces. This was the one exception I made for IoT "cloud…
Woah, I was really considering a Nest (I use Hass.io for many things, lighting at sunset, reading energy meter and my home energy usage), I'm very glad I didn't purchase one yet. One more reason to go for a completely-in-my-lan solution.
Re: Google Is Turning Off the Works-with-Nest API
#445Earlier quoted context omitted.
If you build on someone else's platform, the best case is you get to be a sharecropper and can make money as long as you don't make so much that your platform-betters get jealous. The more typical case is this, where you get to spend your time and money doing real-world R&D and discovery of what works for them, for free. If you're going to dance with a vampire, don't be surprised when it bites you.
One way or the other aren't most of us building for someone else's platform anyway?. Mobile, desktop, browser...
Re: Google Is Turning Off the Works-with-Nest API
#446Earlier quoted context omitted.
Google has done this again and again with their APIs and services other than their main search and advertising business. For me as a developer Google has a bad name now and I'd never invest my time developing something in their ecosystem or worse have my business depend on it. They do not care about their user base as is shown even when they shut down paid services. Which is why even with all their promises about Goo…
I've been a Google apologist for most of my HN career, but shutting down Inbox really changed my view. Regular old GMail sucks compared to Inbox, especially the mobile app. I miss the Inbox app and its layout and recognition of important emails so much that I don't feel like I can get attached to anything else they make.
Re: Google Is Turning Off the Works-with-Nest API
#447EU law (because the EU seems to be the only one willing to make these big laws inconveniencing tech) - any IOT enabled product that has the IOT capabilities removed by closing of a service without a simple way for those capabilities to be re-enabled (simple being further clarified in law) can be returned for a full purchase refund up to 3 months after closing of the service.
IIRC there is a law where you can return items for a full refund or exchange if the product was "not fit for purpose", which includes shenanigans like these.
Re: Google Is Turning Off the Works-with-Nest API
#448Earlier quoted context omitted.
[Spoiler alert, Hyperion series] That sounds totally lifted from the Hyperion series, but maybe the idea is earlier than that, does anyone have a proposed source for that idea that's earlier than 1989?
The writers were big Sci-Fi fans. The Asari were heavily influenced by the Minbari of Babylon 5. There are lots of other callouts to classic Sci-Fi in the series.
Re: Google Is Turning Off the Works-with-Nest API
#449> I’m a Works with Nest developer. Will I be able to access and control Nest devices moving forward? > No. The Actions on Google Smart Home platform does not provide open API access to Nest devices, so it cannot be used to access and control Nest devices. Instead, managing and controlling Google Home, Nest, and thousands of third-party smart home devices is done through the Google Home app and the Google Assistant. W…
Yup, they just did a Twitter. I lived through the Twitter ecosystem collapse and now I'm a VC I worry about investing in startups that are built on any large ecosystem where there isn't an alignment of clear economic interest. Google of all people doing this just made it tougher for everyone else to maintain confidence in large vendor platforms.
That's a way bigger problem than relying on an API or building some app in garden.
Re: Google Is Turning Off the Works-with-Nest API
#450Earlier quoted context omitted.
Developing Microsoft desktop software you're still building on someone else's platform and hoping they don't decide to alter the terms of the deal. Microsoft may be more forward thinking than Google, but companies change.
Absolutely. That risk is much lower than developing for the Alexa, Nest, Twitter, etc platforms. At some point, you’re forced to build on someone else’s platform(s), even if that platform is “Intel” or “AWS” as no one is doing the entire end-to-end value chain.
Proprietary platforms lure developers to their stack by making development easy. Learning an open source is typically more difficult, but the reward is greater freedom. Believing you're forced to build on proprietary technology is a fallacy.