Certification Process

Once you've become a registered Helio Developer, and Helio has selected your application(s) for publishing, you will be able to submit them directly to the Helio Developer Portal. Once a Helio administrator has reviewed your submission(s) and assigned them priority in the queue, they will automatically enter the Helio certification and publishing process. At each stage in the certification and publishing process, you will receive automated alerts notifying you of changes in application certification status. You may also visit the Helio Developer Portal to review the status of your applications at any time. Once your application is certified, it will be added to our publishing schedule and published to the production Helio production catalog.

Helio Certification Process

1. Developer Registration. Register as a developer at http://developer.helio.com. You must have a contract in effect with Helio prior to using the Helio Developer Portal. Any unrecognized registrants and/or application submissions will be deleted.
2. New Application Submission (A). Logon to your personal portal and submit a new application.
3. Automatic Analysis (AA). This process takes place automatically once an application is submitted. The developer will receive confirmation of pass or failure with a QA report outlining the results of the assessment.
4. Submitted Application. The application has passed the initial automatic certification and is in the queue waiting for Market Assessment.
5. Marketing Assessment (MA). Once the application passes the initial Automatic Application Assessment, the Marketing Team is notified, and the application goes through Market Assessment. This process involves the evaluation of a number of criteria including usability, playability, marketability, legal and copyright searches and a number of other tests. If the application passes Market Assessment, the application is placed in the certification queue for complete quality assurance testing and final certification.
6. Quality Assurance Testing (QA). The application is assigned to a QA team member to complete emulator, device and network certification. In the developer portal the status is depicted as 'In Progress'.
7. Pre Certified. The application has passed initial device and emulator certification and is in the process of completing network certification. This is a crucial milestone to achieve as it drives the distribution of the application. Once pre-certified, the application is placed into the Helio application catalog.
8. Certified. The application has passed device and network certification and is placed in the queue for launch.