Live data from Hacker News

Developing for the Amazon Echo

medium.com

1–10 of 17 posts

Re: Developing for the Amazon Echo

#4
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

#6
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

#8

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://w…

Thanks

Re: Developing for the Amazon Echo

#9
post #4

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.

Yeah, it was half QA process.
Post reply on HN