AWS Certified Alexa Skill Builder - Specialty

Users can interact with an Amazon Alexa skill using both voice and non-voice methods in several ways. Scrolling through a list can be done via voice commands (e.g., 'next page') as well as by using touch on a compatible device. Selecting an action is also achievable by voice (e.g., 'select option 2') and touch input. Pausing a video can be controlled by voice commands (e.g., 'pause video') and through physical interactions on the device's screen or remote control.

To accurately track the number of times users launch the skill, the Builder should use persistent attributes that are stored and retrieved from Amazon DynamoDB. This approach ensures that the launch count is maintained across sessions and device reboots. Session attributes are only temporary and reset after each session, while a global variable would not persist state across different invocations. Performing a scan of the DynamoDB table and counting records would not be efficient or accurate for tracking individual user sessions.

On Amazon Alexa enabled devices with a screen, certain built-in intents are handled directly by Alexa and not forwarded to the skill. These include intents used for navigation and displaying more content, such as AMAZON.MoreIntent, AMAZON.ScrollDownIntent, and AMAZON.NavigateHomeIntent. These intents are specifically designed to enhance the user interface experience on devices with screens.

To set up an Amazon Alexa skill beta test, the user identifier that should be used to add beta testers is the Alexa user email address. This helps in identifying and inviting specific users to participate in the beta testing phase of the skill development.

To implement the AudioPlayer interface in a custom Alexa skill, the two essential built-in intents are AMAZON.ResumeIntent and AMAZON.PauseIntent. These intents are necessary because they handle the ability to pause and resume audio playback, which are fundamental controls for any audio streaming capability.