We're starting to see scattered reports across a variety of global regions that there is a new wake word - "COMPUTER" - starting to roll out as devices get the newest firmware. For us here at 3PO-Labs this comes as no surprise, as we noted over a year ago - at the same time we predicted the "ECHO" wake word - that they had special logic for "COMPUTER" already built-in but not complete. This provides us an opportunity to dive back in and see if there's anything new to uncover. Read on for some more technical details, and a running list of the information we can collect...
Just a quick note that "Actions on Google", the Google Home equivalent to the Alexa Skills Kit, is now out of its closed beta. We'll have more to say about this later, after we've had an opportunity to look through the various content provided here: https://developers.google.com/actions/
In the meantime one of our frequent collaborators - Jo Jaquinta of TsaTsaTzu - has already dove head first into Actions with Google, and will be doing a webcast this evening, Friday, December 9 at 6PM PST. You can watch it on Youtube: http://youtube.com/jjaquinta/live
We here at 3PO-Labs are very curious folk. It's our drive to reverse engineer and deconstruct that initially pushed us to build Responder, so we could poke and prod at the system. This same nature is what led us down the path of discovering the third wake word a few months before it was released. In that same vein, today we want to talk about another secret (but admittedly limited) aspect of the platform that we believe has not previously been discovered...
We're super excited to introduce to you our newest Alexa Skill, AstroBot. AstroBot is an aggregator of a few space related APIs, originally inspired by the simple-yet-brilliant howmanypeopleareinspacerightnow.com. Details, attributions, etc, after the break...
So, Tuesday was the big "Made by Google" event, where they promised that all would be revealed. Leading up to it, the hype train was going full steam ahead. We here at 3PO-Labs don't have opinions about most of the announcements (alright, so maybe we have an opinion about whether we need another VR platform), with the exception of Google Home. On that front, we could talk for days...
Just wanted to make a quick note that our name has changed. For the last year (almost to the day) we have been known as DERPGroup, but moving forward we'll be going by 3PO-Labs. We're still building things, breaking things, and talking about everything we love and hate in voice interface. It's just under a different name now.
Our last two posts - about our screwup and about Holocron - have been fairly fun and lighthearted. Aside from the wordplay in the title, this is not one of those posts. Amazon has begun down a path, and we need to talk about why this is a really, really bad move for the platform and for us as developers...
Currently Alexa only recognizes English words. Amazon is just now starting to roll out support for other languages, with German up first. But, what if you want it to match words that aren't words?! That's crazy you say? Or is it?!! We encountered this problem, and this post is going to explain how we approached and solved it.
We're 3PO-Labs. We build things for fun and profit. Right now we're super bullish on the rise of voice interfaces, and we hope to get you onboard.