Recently, the ability to launch 3rd party skills from routines was added. The implementation, however, was minimal. All the user can do is launch the skill. They cannot launch a specific intent.

To unleash the potential of 3rd party skills in routines, users should be able to specify skill intents in the routine: "Tell skill x to y"

Please add the Vietnamese language so users can talk to Alexa in Vietnamese. We love Alexa!

Allow development skills to be used in routines. If we develop a skill, and haven't published it yet, but it is enable and active on our devices then we should be able to use it within a routine (obviously on our own devices).

Would be lovely if Alexa'd have russian language support. Some friends of mine and I were thinking of bringing Alexa to grandparents as they don't use any smart devices and speaking would be the easiest way for them.

having alexa blast "playing from <device name>" is very annoying and there is not setting to turn it off. I would like to propose that a setting be added or that "brief mode" would mute these bluetooth connection/playing notifications.

There is a question related here: https://www.amazonforum.com/s/question/0D54P00006zStJTSA0/how-do-i-stop-alexa-from-telling-me-its-connected-to-my-phone

Allow developers to add multiple email addresses in the Dev consul under the certification tab to receive feedback pertaining to the skill. In addition place the feedback in the certification tab instead of just having a general message that is of no value to the developer.

Move audio to another device, i.e. I’m done in the kitchen and want to continue listening in the dining room. “Alexa,follow me to the dining room.”

Please add Dutch language support for Alexa and make it available in The Netherlands.

You can contact me if there is a beta program or if I can help with voice recognition.

ISP requires a "purchase"-intent to be available in the interaction model, currently every developer implements his own "purchase"-intent with his own utterances. This is not user friendly, as a user cannot rely on being able to use learned utterances from "skill A" in "skill B". So my idea is a new standard built-in "PurchaseIntent".

Change the volume of all devices, so you can change the volume of all devices at the same time not only a single device. For example if you wrote a routine called “night time” you could set all devices to a lower preset volume so as not to be so loud. Alternatively in the morning you could say “morning and all devices volume could be increased to a preset volume. And so on

I have somo lock systems that need to pass a PIN to backend, can this feature be added to LockController interface?

When you add a Music routine without specifying a length, you effectively halt the routine, no actions after that will run. I don't know if there are other actions that do this. If there were an checkbox or something in each action to "Allow routine to immediately continue" after the current action starts, this would fix the issue. Thanks, have a great day.

Have AMAZON.Number accept decimal points in user verbal input. Right now, it handles 'minus' or negative numbers, but not when there is a decimal point.

APL video "loaded" event to enable showing a screen before a video has fully loaded so that the user is aware that the media is still loading. e.g., "Loading..." Right now, APL only has events for after the video has started playing. This is too late to elegantly switch from a "loading" screen to the video.

It would greatly help if the Deploy button, under the Code tab, could check and warn if there were any code errors before deploying the lambda code. Right now I can deploy code with error or even an empty js file. Ideally, the Deploy operation should fail or stop with a good message.

The current limit is 4 minutes. Our app plays backing tracks for guitarists and this is way too short. Please increase to at least 20 mins.

Alexa lacks support for garage door openers in German. We have customers requesting this feature. Our skills supports it, but German users cannot use it because Alexa support is absent.

Response from certification team:
One of the language variants of your Smart Home skill includes functionality that is not yet available for Alexa in that language. Please remove any unsupported functionality from the skill before resubmitting.

Unsupported Functionality: security garage door
Language(s) Impacted: DE