Slashdot Mirror
Google Now Lets Developers Write Apps For the Assistant On Google Home (techcrunch.com)
Google today announced it will open up Home to third-party developers, allowing all developers to start bringing their applications and services to the Google Assistant. Developers can start building "conversation actions" for the Google Assistant, which "allows developers to create back-and-forth conversations with users through the Assistant," writes Frederic Lardinois via TechCrunch. "Users can simply start these conversations by using a phrase like 'OK Google, talk to Eliza.'" TechCrunch reports: While the Assistant also runs on the Pixel phones and inside the Allo chat app, Google says it plans to bring actions to these other "Assistant surfaces" in the future, but it's unclear when exactly this will happen. To help developers who want to build these new Conversation Actions get started, Google has teamed up with a number of partners, including API.AI, GupShup, DashBot and VoiceLabs, Assist, Notify.IO, Witlingo and Spoken Layer. Google has also allowed a small number of partners to enable their apps on Google Home already. These integrations will roll out as early as next week. Given that users will be able to invoke these new actions with a simple command (and without having to first enable a skill, like on Alexa), Google's platform looks to be a rather accessible and low-friction way for developers to get their voice-enabled services to users. Google will have the final say over which actions will be enabled on Google Home.
Google just screwed up on Google Home. Amazon echo had SDK access from the get go, not months after launch.
Here are some more items:
1) Walled garden approach, no one except a few companies had ability to integrate before launch.
2)Stupid Android/iOS App only for configuration and setup. Echo has both App and web interface.
3) Me too , late to the game, the Echo was release in Nov 2014.
4)No bluetooth or stereo jack.
5) Home automation support is current limited to 3 official products, good thing there is Hue Bridge, otherwise my 60 or so smart home devices wouldn't work.
5) Google Home sucks for name, a few weeks ago searching for anything Google Home brought you articles about the Google Homepage.
The only good thing it has going for it is the speech is better than Amazon by slight margin and it is bit quicker than the Echo.
Hoping Google turns it around a bit.
regular uni bomber have you created your at tech manifesto yet.
... using your finger, then you're probably too goddamn lazy to read the instruction manual to all this solution-looking-for-a-problem home automation basement dwelling nerds wet dream bandwagon that every company is jumping on because they can't actually think of anything original and useful.
I'm going to design a pocket sized RF pulse generator that will fry the first stage of the RF receivers in nearby phones
You should probably do a some research on the power requirements to destroy a cell phone at any significant distance and the energy density of available power sources before you make statements like that.
The only viable EMP devices that could destroy nearby cell phones and still fit in your pocket are explosively pumped flux compression generators. As the name suggests, they explode, which isn't usually something you want happening in your pocket.
tl;dr - These already exist, but they'll blow your junk off.
Google Home only comes with a 1 year warranty. This is exactly the same length of time that Revolv Hub users had. Once the warranty ended, Google indicated it had the right to intentionally brick the device. I don't want to spend $129 on a device which is set to die by policy in just 12 months. And I really do not want to take the time to write to an API to encourage others to buy into the scam. Given how Google has clarified their policies to be so anti-consumer, I don't see how anyone could see this product worth spending time or money on.