Static "settings" slots, configurable on a per-device basis
Use case : Passing slot values to Skills that you don't want to require the user to have to specify every time. Examples : * A "home station" for a transit app (i.e., only the destination station needs to be specified because the origin is already known) * A "room name" for a home automation app ("Alexa tell Smart Things to turn on the lights" runs a different scene on the upstairs bedroom Echo vs. the living room Echo) In both cases, these are parameters that will change from device to device, but do not change on a regular basis. As with the location example mentioned in another thread, it's certainly possible to have the Skill obtain these from the user using some out-of-band mechanism, but this adds unnecessary complexity to the development of the Skill (e.g., web-based settings UI, need to securely store potentially personal information, etc.) and, if multiple devices are tied to the same account, makes it problematic to implement device-specific settings (like the "room name" mentioned above). Both of these issues would be addressed by the device having settings available on a per-skill basis (similar to the way that Zip Code already works). Message was edited by: Mark E. Fogle
I think what you want for this is for the request to come down not just with a userID but also a deviceID. Then you could distinguish between them and set your stuff up accordingly. Beyond that, what would also be nice to fulfill this would be to be able to contribute a panel to the Settings selection on the companion app. I.e. once they've enabled your skill, the panel would be available. You could have whatever UI you want in there to set up your app.
Thank you for your feedback. The SDK team is aware of your request and may investigate a potential solution for future releases. We appreciate your participation and interest in Amazon's Alexa Skills Kit developer program.