Alexa for Apps FAQ
Important: Alexa for Apps is a developer preview and might change as Amazon receives feedback and iterates on the feature. To use this feature, you must register for the preview. If you have questions or feedback about Alexa for Apps, please email firstname.lastname@example.org.
Alexa for Apps FAQ
- Q: What changes must I make in my app for Alexa for Apps to work?
- Typically, none. If users can open your content and features with existing deep links, you don't need to make any changes. If you don't already have deep links in your app, you must add them. For details, see Alexa for Apps supported deep link types
- Q: Does the Alexa for Apps user experience end after users get into my app?
- Users can use voice to get to the desired place within your app or website. After users are there, they can transition to touch, or start a new request to your skill. For example, "Alexa, ask Cupcake Shop where's my order?"
- Q: What if the user doesn't have my app installed?
- In that case, you can redirect them to the iOS App Store, the Google Play Store, or your website. Universal deep links always fall back to the website associated with the deep link.
- Q: Can users access my Android or iOS app from a nonmobile Amazon Echo device?
- During the developer preview, users must invoke your skill from the Alexa mobile app, an Alexa mobile accessory such as Echo Buds, or an Alexa built-in phone.
- Q: In which locales can I use Alexa for Apps?
- Any locale that Alexa supports. For the current list of supported locales, see The Alexa Skills Kit around the World.
- Q: Can I customize the user experience for Alexa for Apps?
- Yes. Because you use Alexa for Apps links with custom skills, you have the flexibility to create a combined voice-and-touch experience for any user intent. You can start with a simple skill that just provides voice shortcuts via deep links to key features in your app. Or, at the other extreme, you can create a rich multi-turn voice experience. This experience, when appropriate, sends the user seamlessly into your app using deep links with query parameters to maintain context for the user's request. You can even customize responses for different device states, such times as when user isn't likely to be looking at their phone. For example, when a user has locked their phone, you can provide a more verbose response.