How We Validate Your Application or Component

Application validation consists of several steps.

1. Check your submission information (rating, categories, submitter notes, intended targets and runtimes, etc.)
2. For applications targeted for the MeeGo* operating system, we run MeeGo compliance-checking tools.
3. Install the application on the appropriate operating system.
4. Run several types of validation tests to check for compliance to the submission guidelines.
5. Check the application against your submission criteria.
6. Pass or Fail the application/component.
7. Notify the developer of the results.

Even though your application passes all the validation tests, Intel reserves the right to reject a submitted application/component or remove a published application/component for any reason deemed appropriate.

What We Look For

The validation process checks several key areas as appropriate for applications and components. Application validation areas cover the following:

• Security and Protection - checks for unacceptable behavior that can result in harm to other software or networks and acquires or uses privacy information without explicit consent by the user.
• Licensing and Trademarks - checks for violation of Intel trademark rules and checks that you have the rights to sell and distribute the code.
• Installation/Uninstallation/Operation - checks that the application can install and operate, and uninstall, without creating other operational problems on the system.
• Submission - checks that the application is rated appropriately, categorized accordingly, and contains no objectionable content.
• Prohibited Activities - checks for disallowed activities, such as pop-ups and particular types of advertising.
• Functionality - checks that the application and user interface functions as intended, the user interface is consistent, and the application meets any other operational requirements.

Component validation areas cover the following:

• Licensing - checks for a license document.
• API Documentation - checks that the API is documented.
• Testing - checks functionality according to provided tests (in the case of open source code) or user documentation (in the case of proprietary code)

For details about validation checks, see the Validation Guidelines document and download the Application Readiness Checklist or Component Readiness Checklist.

What Will Automatically Cause Your Application to Fail Validation

Your application will be automatically rejected for any of the following (this is not a complete list):

• The application is incorrectly packaged. See the Packaging Requirements Guide .
• The category or rating selected is not consistent with the content.
• The application contains objectionable content.
• The code contains malware.
• Appropriate warnings and opt-ins/opt-outs are not in place when collecting personal data or when using certain external resources, such as GPS.
• There is no license or user documentation where it is required to use the application or component.
• Improper use of trademarks.
• The code triggers pop-ups.
• The code is not in compliance with MeeGo* operating system requirements.

For details about conditions that cause rejection, see the Validation Guidelines document and download the Application Readiness Checklist or Component Readiness Checklist.

Ensuring a Smooth Validation

Before you submit your application for validation, be sure you have done the following:

• Packaged it according to the Application Packaging Requirements Guide.
• Reviewed the Validation Guidelines document.
• Tested your application internally.
• Downloaded and reviewed the Application Readiness Checklist or Component Readiness Checklist.

Checking on Your Validation

After you submit your application or component, check your Dashboard for the validation status. Validation status appears below the application or component name in your Saved Applications and Saved Components lists.

If your submission passes, the validator notifies you by email, and your publishing information appears below the application or component name.

If your submission fails, status and error codes appear below the application or component name. You also receive email with more details.

If Your Submission Fails

If your submission fails, check the following for more details.

• Check the failure code against the Validation Guidelines document. This document lists the failure codes and the tests that return them.
• If the failure was caused by a component, check the component's support page or contact the component developer.
• Revise your code.
• Resubmit for validation.