The developer console has some great analytics around Customers, Sessions, Intents, and Utterances, but when building a skill that uses Gadgets, the metrics don't have as much meaning depending on how the skill was written.
Propose to add a new metrics that tracks the number of events created by gadgets like Echo Buttons, and either augment the existing analytics, or abstract what an utterance is to be an event so that gadget triggered events also are counted on the analytics pages.4 votes
Currently you need to do rollcall to find out if a user has echo buttons. But it seems like a bad user experience to do button roll call or ask a user if they have buttons. If we could get sent something on launch saying user has used buttons before or connected them previously or currently has them connected then we know we can try roll call or ask them if they want to use buttons.
Current solution seems to be to build a separate skill for buttons.4 votes
For Echo Buttons:
1. A way to make roll call less extensive. I understand the logic behind finding the buttons. It would be nice if you could quickly press all of the buttons, especially for games that don't tie a player to any single button. With four buttons it is really time intensive.
2. Ability to connect more than four buttons. Four buttons limits the skills you can develop with the buttons.
3. Fixing the latency.2 votes
It is possible to launch Alexa Skills on the FireTV Stick, but not the ability to connect the echo buttons with the FireTV.
When playing game skills with friends we are used to start the skills on the bigger TV screen on the FireTV. Therefore it would be awesome if we could also play game skills which require echo buttons.2 votes
I think it would be better for the user experience if gadgets have the ability to reconnect automatically to Alexa without requiring the user triggering it. If the gadget did already pair with Alexa why need the user to trigger reconnection ? As a user that's what i would expect.1 vote
All the capabilities in this Alexa Gadget Toolkit announcement are focused around triggering gadget behaviors based on Alexa-initiated events. What about the other way around? Please make it possible to have a Gadget trigger a response from Alexa.1 vote
- Don't see your idea?