APL - Don't stop skill when a user interacts with components
Presenting an APL document that includes components such as a ScrollView, for example, invites the user to interact with that component. Unfortunately, as soon as the user touches the screen, the skill stops. If Alexa was speaking, she abruptly stops speaking. If the user does nothing more, the skill comes to an end and the user is kicked out. This is a horrible experience.
Add the ability, for developers to present either certain components that won't interrupt the skill, or a full document that won't react to touch.
Jeff Savin
shared this idea
-
Cyrus Adkisson
commented
I think this may be resolved or improved. I'm seeing that new requests don't fully interrupt long-running commands in my application anymore.
-
Cyrus Adkisson
commented
This is a huge headache for me at the moment. We need to take user input during a long scroll and any input stops the scroll, throwing everything off. Upvoted.
-
Anonymous
commented
Hi everyone! Is there an update to this?
Thanks,
Sergey