Settings and activity
3 results found
An error occurred while saving the commentDavid Nogueira shared this idea ·
An error occurred while saving the commentDavid Nogueira commented
This should be a feature already implemented. It is of the utmost importance for software developers and contractors to be able to develop apps for clients on their own account and then transfer ownership (without having to create sharable dummy accounts for every new skill).
Allow developers to be able to define callbacks for user interruptions.
At the moment, as soon as Alexa start responding to the user, he must listen to the full response or quit the app.
There's no option to suppress current response and stay in the app.
Consider an example:
Alexa: I found three news articles related to your query. Article #1: [title of the article] Article #2: [title of the article] Article #3: [title of the article]
Assume that the app allows the user to then listen to the full article. He needs to wait for the full message to be read before he can interact.
It would be much more interactive and real-life like if the user could interrupt and ask "Read me this article", and that would activate a callback function, that the developer would be able to define.
Currently, the only way to have this functionality is to force users to wait until the end of the message and then say something like "Read me the second article".
That callback function would receive as argument the user command plus the word/sentence that was being spoken when the user interrupted, which would allow for faster interactions.