News for hackers. Stuff that matters.
Re:Developing for the Amazon Echo by willu on Wednesday April 13, 2016 @10:35AM (#11488509)
I'm actually impressed by the level of detail provided in the rejections. There's nothing worse than getting a rejection that does not clearly state the reason for the rejection and a path to resolution. Apple and especially Google are notoriously bad about this.
Re:Developing for the Amazon Echo by genadyo on Wednesday April 13, 2016 @12:14PM (#11489494)
Yeah, it was half QA process.
Re:Developing for the Amazon Echo by mikeflynn on Wednesday April 13, 2016 @12:11PM (#11489466)
You definitely can get an Alexa skill off the ground without using Lambda, but there are a lot of little details with their authentication to work out. I'd highly recommend one of the libraries that are out there:

Go - https://github.com/mikeflynn/go-alexa/tree/master/skillserve... (full disclosure: I created this one)

Offical Java SDK - https://developer.amazon.com/public/solutions/alexa/alexa-sk...

Node - https://www.npmjs.com/package/alexa-app

...to name a few.

Re:Developing for the Amazon Echo by blandflakes on Wednesday April 13, 2016 @04:18PM (#11491819)
Re:Developing for the Amazon Echo by genadyo on Wednesday April 13, 2016 @12:13PM (#11489490)
Thanks
Re:Developing for the Amazon Echo by nickclaw on Wednesday April 13, 2016 @01:03PM (#11490046)
Shameless plug for my node skills framework[1] if you want something a little more flexible than alexa-app. Has express support as well[2].

[1] https://www.github.com/nickclaw/alexa-ability [2] https://www.github.com/nickclaw/alexa-ability-express-handle...

Re:Developing for the Amazon Echo by bonobo_34 on Wednesday April 13, 2016 @06:15PM (#11492772)
This article sums up my recent experience trying to get a skill published. It was slightly frustrating to receive multiple rejection emails, but at least the responses were detailed and helpful.

While building some skills for fun, I also made some gulp tasks for locally testing skills and deploying the code to your lambda. https://github.com/tmcleroy/alexa-skills

Re:Developing for the Amazon Echo by jackcarter on Wednesday April 13, 2016 @12:29PM (#11489651)
I built a similar app for Chicago's CTA trains, called CTA Tracker. There seem to be train tracker apps for most major cities, since they're easy to implement and legitimately useful.
Re:Developing for the Amazon Echo by altryne1 on Wednesday April 13, 2016 @12:09PM (#11489443)
Nice write up! I can't wait to start developing for my Echo!
Re:Developing for the Amazon Echo by genadyo on Wednesday April 13, 2016 @12:14PM (#11489500)
Just do it!
Re:Developing for the Amazon Echo by wyldfire on Wednesday April 13, 2016 @10:23AM (#11488405)
Aside:

> NextTrain {FromStation} to {ToStation}

Does Echo have some concept of scoping for these skills? Or do you have to opt-in to the skill?

Re:Developing for the Amazon Echo by Linell on Wednesday April 13, 2016 @10:28AM (#11488444)
You have to opt into the skill by enabling it via the app that was mentioned in the post.
Re:Developing for the Amazon Echo by dkopi on Wednesday April 13, 2016 @12:42PM (#11489809)
Great write up. I wonder how developers can actually profit from developing apps for echo
Re:Developing for the Amazon Echo by gariany on Wednesday April 13, 2016 @12:11PM (#11489472)
damn, this changes a lot. I was scared of Amazon Echo (or any other retailer's product) listening to me 24/7, but I guess it can't be avoided
Re:Developing for the Amazon Echo by stronglikedan on Wednesday April 13, 2016 @12:59PM (#11490008)
Why would you be scared? The keyword(s) is processed locally, and it only sends the request following the keyword over the wire. If they tried anything fishy, such as sending everything it hears over the wire, then they would be outed within a day.
Re:Developing for the Amazon Echo by azinman2 on Wednesday April 13, 2016 @01:21PM (#11490191)
It also makes a sound (tho not by default) and lights up whenever it's listening.