Hello Developers,
As we approach device launch, in alignment with Fire OS quality standards, we’re reinforcing our app testing protocols to maintain exceptional customer experience. Starting September 30th we are aligning our app testing process with Fire OS by implementing end-to-end (E2E) testing during the submission phase. Previously, E2E testing was conducted after publishing without blocking app releases. Under the new process, apps that fail E2E testing will be rejected and returned with detailed feedback, including reproduction steps, logs, and video documentation of the issues identified. Please review the Submission Guidelines Developer Doc Link before submitting your app to ensure a smooth approval process.
Launch-Ready Applications: Once your app is prepared for launch, we recommend maintaining its current state and avoiding further submissions or backend modifications, except for critical updates or changes requested by your Amazon contact.
Apps Under Development: For unresolved blockers and/or in-flight feature integrations, maintain communication with your Amazon contact. When submitting feature integrations, we strongly recommend utilizing Live App Testing (LAT) for feature certification before submitting your updates to the Appstore.
Frequently Asked Questions
Q: How do I know my app is ready for launch?
An app is launch-ready when all its core functionality is ready, planned feature integrations are complete (e.g. Content Launcher, IAP, Content Personalization, Live TV, etc.), it’s meeting the performance KPIs and is currently available in the Appstore. If in doubt, please reach out to your Amazon contact.
Q: What is the app testing criteria?
A: Consistent with Fire OS process, the app testing criteria is a comprehensive validation process that tests your app’s functionality from start to finish, ensuring all features work as intended in a production-like environment.
FIle Download:
Important: Amazon Confidential. Amazon offers this technical documentation as part of a pre-release, private beta.Function test - Confidential.docx (26.3 KB)
Feature Integrations Test Criteria
Q: What happens if I discover a blocker issue in production before launch or post launch?
A: Work with your Amazon contact to determine a plan to fix the issue and expedite publishing it to production, or revert to the last known good version of your app.
Steps to revert:
- Retrieve the last known good version from your version control
- Increase the version number in manifest and rebuild
- Submit this new build to Appstore to replace the broken version
- Contact your Amazon representative if you need assistance
Q: Are there any block days for submissions before or after launch?
A: About two weeks before launch we will reach out to you to communicate the launch date and any block dates accordingly.
Questions? Use the Q&A section or reach out to your Amazon contact directly.