Today on 17.04.2021 at 10:15 AM, I experienced a situation where two skills appear at the same time. They are reading amazon order notifications and executing routine.

The routine was set by me which is running on scheduled time after a specific interval. The detailed information is given below:

Previously, I set a routine on weekly basis(Saturday at 10:15 AM). However, at that time(10:14 AM), there a notification arrived about my amazon order.

So, I requested Alexa to read my notification and Alexa read it for me. Fortunately, my request and the routine execution time were the same(10:15 AM), as a result, the routine was not executed.

My suggestion for this type of scenario is, if 2 or more skills suddenly appear in Alexa at the same time then it will be better to make a temporary waiting list based on priority or any parameters and execute all one after another by maintaining minimum pause duration.

For example: in my case that is described above, I am expecting the following a temporay waiting list and execution from Alexa.

1. Execute my weekly routine, then


2. Read the recently arrived notification

Now, why I want Alexa to execute my routine at first because I set it previously and It has been continuing since last week.

Then, I want Alexa to execute my request to read the notification.

I hope, I can explain the situation in an easy and understandable way.

Thanks in advance.

The AnimateItem command can be used to create animations for the opacity and transform properties. With the release of APL 1.6, many more properties have been unlocked for dynamic updates, such as the height and width of a component.However, the AnimateItem command does not support these properties, instead you have to use for example Easing Functions to implement animations for these properties. In my opinion, the Easing Functions are relatively complex in terms of their structure, and furthermore they can currently only be defined statically, which means that, as with the AnimateItem command, I have to define the initial and final state. For static layouts this approach may work, but not for flexible layouts which are generated using the Datasources and Data Array Inflation method.

My wish for a new APL version would be a transition property to define how a property should be animated after it has been updated using the SetValue command.

Example:

```
"items": [{
"type": "Frame",
"backgroundColor": "transparent",
"transition": [{

"property": "backgroundColor",

"duration": 1000,

"delay": 500

}, {

"property": "transform",

"duration": 1000,

"delay": 500

}],
"transform": [{

"rotate": 0

}],
"onMount": [{

"type": "SetValue",

"property": "backgroundColor",

"value": "blue"

}, {

"type": "SetValue",

"property": "transform",

"value": [{

  "rotate": 45

}]

}],
"item": {

"type": "Text",

"text": "backgroundColor animation"

}
}]

```

Also, it would be nice to have handlers to react to these state changes.

```
"items": [{
"type": "Frame",
"backgroundColor": "transparent",
"transition": [{

"property": "backgroundColor",

"duration": 1000,

"delay": 500

}, {

"property": "transform",

"duration": 1000,

"delay": 500

},, {

"property": "width",

"duration": 100

}],
"transform": [{

"rotate": 0

}],
"onMount": [{

"type": "SetValue",

"property": "backgroundColor",

"value": "blue"

}, {

"type": "SetValue",

"property": "transform",

"value": [{

  "rotate": 45

}]

}],
"onTransitionRun": [{

"when": "${event.target.property == 'transform' && event.target.value >= 30}",

"type": "SetValue",

"property": "width",

"value": "${event.target.component.width + 10}"

}],
"onTransitionEnd": [{

"type": "Idle",

"delay": 5000

}, {

"type": "SetValue",

"property": "backgroundColor",

"value": "transparent"

}, {

"type": "SetValue",

"property": "transform",

"value": [{

  "rotate": 0

}]

}],
"item": {

"type": "Text",

"text": "backgroundColor animation"

}
}]
```

In my opinion, this construct is much more flexible than the AnimateItem command, and it would also work well with the newly introduced styled properties.

It will be better for the user, to add more than one statement as alternative voice command in the same Alexa Routine instead of creating separately.

For example:

A user creates a routine named "I'm home". The tasks under this routine will be executed when the user says to Alexa "Alexa, I'm home".

However, the user may also say

"Alexa, I'm back" or
"Alexa, I return home" or
"Alexa, I enter in sweet home" or
"Alexa, I enter home" or
"Alexa, I'm back to my room" or
"Alexa, I just arrive" or
"Alexa, I arrive home" or
"Alexa, I reach home" or
"Alexa, I just entered my home" or
"Alexa, I just entered sweet home" and so on.

In the above case, for these example voice commands, the user needs to create separate routines that contain the same/similar tasks like the routine named "I'm home".

So my proposal is either to have the option to add more statements under the "when" text field during Routine creation

or create some possible collection of commands that relates to the user-given voice command.

As a result, when the routine will be enabled, then Alexa will perform tasks after getting any voice commands from the collection.