Version 2.0
Last updated December 15, 2011

Contents

1. Introduction

• 1.1 Overview and Intent

2. Application Store Definitions and Guidelines

• 2.1 Application Definition
• 2.2 Policy Guidelines
• 2.3 Application Packaging and SDK Use
• 2.4 Application Submission Information

3. Application Validation Criteria

4. Component Provider Guidelines

• 4.1 Component Definition
• 4.2 Policy Guidelines
• 4.3 Licenses
• 4.4 Component Submissions

5. COMPONENT Validation Criteria

Appendix: Intel trademark and brand list

1. INTRODUCTION

The Intel AppUp(SM) Developer Program presents an opportunity for developers to create unique and useful applications for netbooks, laptops/PCs, and tablets based on Intel® processors. The Intel AppUp Developer Program also enables developers to create reusable component building blocks that other developers can use in their applications, accelerating application development.

Application Stores for the Developer Program will allow end-users to discover, purchase, and download these applications. The Component Catalog within the Developer Program makes components available to application developers.

1.1 OVERVIEW AND INTENT

The intent of this document is developers fully understand the guidelines used to validate applications and components submitted.

In order for an application or component to pass validation, it must successfully meet pre-defined validation guidelines. An application/component will not pass validation if one or more of the validation guidelines are not met. Note that application/component validation criteria described in this document have been developed by Intel® and may or may not align with industry standard validation tests. Only applications/components that meet the criteria are eligible for distribution.

NOT WITHSTANDING ANY OTHER PROVISION IN THIS DOCUMENT, INTEL RESERVES ALL RIGHTS TO DETERMINE IN ITS SOLE DISCRETION WHETHER TO ACCEPT AN APPLICATION FOR THE APPUP(SM) STORES. THERE ARE NO GUARANTEES AN APPLICATION THAT PASSES ALL VALIDATION TESTS AND THE OTHER REQUIREMENTS SET FORTH IN THIS DOCUMENT WILL BE ACCEPTED FOR DISTRIBUTION --- THESE ARE ONLY GUIDELINES.

2. APPLICATION STORE DEFINITIONS AND GUIDELINES

2.1 APPLICATION DEFINITION

Application as defined in this document means a software program developed by a developer in compliance with the following application submission guidelines: under their own trademark or brand, and for specific use with the Intel AppUp Developer Program

2.2 POLICY GUIDELINES

Applications must meet the following guidelines to pass Intel AppUp Developer Program validation.

Security/malware:

• Applications containing computer viruses, spyware, malicious or harmful code, program, or other internal component (Trojans, etc.) which could damage, destroy, or adversely affect other software, firmware, hardware, data, systems, services or networks will be rejected

User privacy/opt-in:

• Applications that collect personal information without a privacy policy that includes details on how and why personal information is gathered and disclosed will be rejected.
  • Developers who collect personal data will provide
    • Purpose of Collection
    • Notice
    • Opt-in is recommended
• Applications that share information with third parties without the users consent will be rejected. Developer will disclose to Intel whether the application transmits any user's personal data to any other third party via the submission notes area when submitting their application.
• Apps that collect or use location information without the explicit consent of the user will be rejected.
• Applications that access or share user "data" without explicit user permission will be rejected. This includes contacts, phone numbers, photos, SMS or other text communication, browsing history, location information and other data stored on the mobile device or stored in the cloud but accessible from the mobile device.
• Application that record audio, video, or still images without notifying the user that a recording is taking place will be rejected.

App Signing:

All applications targeted for Windows* operating system must be signed by an accepted Certificate Authority:

• Verisign
• Thawte
• Globalsign
• Chosensecurity
• Comodo
• Go Daddy
• TrustCenter

Content:

• The submitting developer is required to either own or have adequate license rights to all content submitted to the Developer Program. For any licensed content, the submitting developer is solely responsible for complying with all terms and conditions of such license, and notifying potential users of the application or component on any compliance issues associated with such third party content, including any open source code and related license requirements.

2.3 APPLICATION PACKAGING AND SDK USE

Application Packaging

• Applications packaged differently than described below will be rejected. Applications must meet the packaging requirements for Windows*, Java*, MeeGo* and Adobe AIR* packages. Packages required are based on OS distribution and checked during installation of the application.
  • Windows* Packaging Requirements
  • Adobe AIR* Packaging Requirements
  • Java* packaging Requirements
  • MeeGo* Packaging Requirements

Use of the SDK

• Use of the Intel AppUp™ SDK is optional for all applications and is not permitted for open source applications. This applies to Windows*, Java*, Adobe AIR* and MeeGo* applications.

2.4 APPLICATION SUBMISSION INFORMATION

Application submissions must include all details necessary to be able to run and fully validate the application. Failure to include such details will result in delays or rejection during validation. Please use the “the “Message (Notes to the Validation team)" field within the submission page to provide information on your application such as:

• Test login or account information
• Location and instructions for accessing and installing any dependent files or applications that are needed in order to run the application.
• If the application is a "demo" or pre-release version, indicate any end user limitations for running the application, i.e. expiration dates, limited functionality

Hardware Shipping (HW): When special hardware is required to validate an application, developers are required to ship two (2) test devices to Intel for use in testing. Application submission notes should indicate all hardware dependencies, that special HW is being shipped, shipper and tracking information for shipping and the approximate ship date.

• Shipping address is: Intel AppUp Validation Lab, c/o NSTL 670 Sentry Pkwy., Blue Bell, PA 19422
• Shipment should include all related validation information necessary in order to match HW with the software application it is to be used with, including application name, version number, submission date, company name, contact email and phone number.
• Shipment should include all necessary instructions for HW setup.
• Developer is responsible for shipping charges and insurance to and from Intel. Pre-paid return shipment information should be included with HW shipment. Either pre-paid labels or supplying a shipping account is required.
• If developer does not require that HW be returned, it should be stated with the submission information.
• Intel will keep the HW in the lab for testing for 8 weeks post the last submission date of the developer's application, unless developer requests otherwise.
• Intel is not responsible for loss or damage to developer submitted HW, either while in the validation lab or during shipment.
• Intel will confirm receipt of HW via email. Intel will confirm shipment back to developer via email.
• Longer validation wait time may occur due to wait times for HW shipment. No guarantees are made by Intel on turnaround time for applications with dependent HW.

3. APPLICATION VALIDATION CRITERIA

ILU01 - Application must download and install from Intel AppUp(SM) Center

• Applications that do not install and run correctly on the target device will be rejected
• The AppUp client recognizes the app as being installed
• The installation is completely silent and does not require any inputs from the user. Exception: On Windows* 7 devices, a User Access Control (UAC) dialog is acceptable during installation.
• Application should also run natively outside of the AppUp client (e.g. Start menu, program files, etc.)
• Windows* PC applications that do not run on 32-bit Windows* 7 Starter Edition will be rejected.
• Windows* PC applications that do not run on 64-bit Windows* 7 Home Premium edition will be rejected.

ILU02 - Application must uninstall cleanly and silently

• Application that require user input to uninstall will be rejected
• Application that have errors during un-install will be rejected
• Applications that do not remove the Icon in the appropriate category with the un-install process will be rejected
• Applications that leave garbage files behind will be rejected. Exceptions to this will be any user related data and/or files.

ILU03 - Application should launch on target device

• Applications that do not launch on the target device when launched from within the AppUp client will be rejected
• Applications that crash or have errors will be rejected
• Applications that do not function as expected will be rejected
• Applications that use licensing mechanisms or keys other than what is provided with Intel AppUp will be rejected.
• When error messages regarding launch are displayed to end users, the Intel AppUp™ client should be referred to as "Intel AppUp(SM) Center".

INC01 - Unauthorized use of Intel Trademark and Brand

• Inappropriate use of Intel trademark and brands will cause application to be rejected.
• Unauthorized use of Intel logos for marketing or within application's local content will cause application to be rejected.

INC02 - Objectionable Content

• Applications that reference or contain any of the following will be rejected:
  • Sex / Nudity - Images that are suggestive or sexual (e.g. exposed breasts, bare buttocks, visible genitals, visible sexual touching, explicit sexual language, erections/explicit sexual acts, bondage/SM, erotica).
  • Content that generally falls under the category of pornography
  • Content that depicts or suggests prostitution
  • Any content depicting sexual fetishes
  • Any content of a sexual nature depicting children or animals
• Applications are self-rated according to the table below. Those that are rated inaccurately will be rejected.

Ratings Guidelines

Rating	Applications with this rating may contain...
3+	Content that is generally considered suitable for children three years of age and older No content that parents or educators would find objectionable No collection of personal data
6+	Mild or infrequent acts of violence to fantasy characters (e.g. cartoons and animation) Minimal advertising suitable for children No collection of personal data
10+	Mild or infrequent acts of violence to fantasy characters (e.g. cartoons and animation) Mild or infrequent depictions of weapons or their use Mild expletives or strong language Minimal content that may set a bad example for children: teaches or encourages children to perform harmful acts or imitate dangerous behavior Minimal content that creates feelings of fear, intimidation, horror or psychological terror Minimal advertising suitable for children No collection of personal data
13+	Infrequent depictions of mild sexual material (e.g. passionate kissing) Frequent or intense depictions of violence against fantasy characters (e.g. cartoons and animation) Mild or infrequent depictions of violence against humans or animals (e.g. death, killing, dismemberment, torture) Frequent or intense depictions of weapons or their use Mild or infrequent use of vulgar or abusive language or swearing Gambling Access to moderated and unmoderated user-generated content (e.g. chat rooms, instant messages, email, etc.) Advertising Collection of personal data (e.g. e-mail addresses, etc.)
17+	Frequent or intense depictions of mild sexual material; violence; potentially offensive language; potentially harmful activities, including depictions of tobacco or its use, alcohol or its use, recreational drugs or their use; potentially disturbing material or content that assumes an adult audience Access to or depictions of nudity or sexual material in an artistic, artistic literature, educational, medical, news, or religious context Unfiltered access to internet
18+ THIS CONTENT IS NOT ALLOWED	Content that generally falls under the category of pornography Nudity or sexual material (e.g. exposed breasts, bare buttocks, visible genitals, visible sexual touching, explicit sexual language, erections/explicit sexual acts, bondage/SM, erotica) Content that depicts or suggests prostitution Depictions of sexual fetishes Content of a sexual nature depicting children or animals

INC03 - Advertisements and payment mechanisms

• Applications may not encourage users to upgrade or purchase their applications or other applications outside of the Intel AppUp(SM) Center. Examples:
• Purchase links, buttons, or images which direct users to purchase or download outside of the Intel AppUp Center are forbidden.
• Homepage links, buttons, or images directing users to a web site or sites containing applications available for download and/or purchase are forbidden.
• - Applications may not use payment or advertising mechanisms other than those provided by Intel through the Intel AppUp Center. However, the following exceptions are granted for applications submitted by June 30th 2012:
  • Applications that utilize content purchased outside of the Intel AppUp Center. For example: book content for a free e-book reader, magazine application content, video or music content that can be accessed by applications within the Intel AppUp Center.
  • In-app payments and subscription content.

Applications with the above exceptions will be permitted in the Intel AppUp Center through December 2012.

UIX01 - All menus, graphics icons and text must be clearly readable by user

• Must use full screen capabilities, if applicable to the app. Definition of full screen varies with various manufacturers (see table below for sample device display size).
• Must use input capabilities applicable to the device.
• Applications with overlapping text, truncated text, graphics issues or distortions, color bleed and incorrect displays will be rejected.

Sample Devices:

Platform/Device/Manufacturer	Display size	Display Resolution	Video Chipset
Notebook - 900X3A/Samsung	13.3	1366 X 768	Intel® HD Graphics 3000
Notebook - Acer Aspire* S3/Acer	13.3	1366 X 768	Intel® HD Graphics 3000
Ultrabook – Asus Zenbook*- UX21E	11.6	1366 X 768	Intel® UMA
PC- Lenovo ThinkPad*- T410	14.1	1440 X 900	Intel® HD Graphics
PC- HP Pavilion*- DV6-3236 NR	15.6	1366 X 768	Intel® HD Graphics
MeeGo* Netbook- Asus EeePC* 1015PEM	10.1	1024 X 600	Intel® GMA 3150
Windows* 7 Netbook- Samsung N150*	10.1	1024 X 600	Intel® GMA 3150

UIX02 - User Interface consistency must be preserved across the application

• Applications Menus and user inputs that do not function as expected will be rejected

OSI01 - Application is MeeGo* compliant and runs on MeeGo* compatible devices

MeeGo* applications must be MeeGo* compliant: http://wiki.meego.com/Quality/Compliance

GEN01 - Application Submission Information and General Functionality

• Application submission information includes all necessary login details, instructions and hardware/software to perform testing. Applications that cannot be validated due to missing, incomplete or inaccurate meta data of functionality errors will be rejected.

DES01 - Content and description fields are error free and adhere to content submission and validation guidelines

• Apps using inappropriately licensed IP will be rejected.
• Licensed content is only allowed where:
• Content and App Name is original
• Copyrighted content is used with appropriate permission
• Branded items (logos/trademarks) have been approved by brand owners
• App metadata content and materials must fall in or below the 3+ Application Content Rating irrespective of app content rating selected by the developer.
• Apps with significant spelling or grammatical errors will be rejected

DES02 - Email addresses and Support URLs are valid and function as appropriate mechanisms to get in contact with Developers

• Apps with invalid support email addresses or URLs will be rejected

DES03 - Custom end user terms and conditions are compatible with program models and objectives

• Apps with a Custom EULA that doesn't allow usage on 5 devices will be rejected
• Apps with a Custom EULA that conflicts with the standard Intel EULA will be rejected

IMG01 & 02 - Icons and screenshots are appropriate and adhere to program policies and guidelines

• Icon falls in or below the 3+ Application Content Rating irrespective of app content rating selected by the developer.

4. COMPONENT PROVIDER GUIDELINES

4.1 COMPONENT DEFINITION

Component as defined in this document means a software module offered as an independent modular and reusable building block for developing an application. Components enable reuse of software parts over multiple applications. Components are characterized by having a well defined and documented interfaces and dependencies which describe the access points, parameters and all functional and non-functional behavior and conditions for using the component.

4.2 POLICY GUIDELINES

Components must meet the following guidelines to pass Intel AppUp Developer Program validation.

Security/malware:

• Components containing computer viruses, spyware, malicious or harmful code, program, or other internal component (Trojans, etc.) which could damage, destroy, or adversely affect other software, firmware, hardware, data, systems, services or networks will be rejected

4.3 LICENSES

All third-party software components have individual software license agreements. The individual licenses for any of the components in the Developer Catalog will be included in the components.

Ultimately, it is the component providers' responsibility to ensure that their choice of license is clear to all who may use, modify or distribute their components. Application developers who plan on using components published in the Developer Catalog are encouraged to contact the component copyright holders directly in order to clarify any questions or concerns regarding the appropriate license.

The following template is used to describe the criteria and results.

4.4 COMPONENT SUBMISSIONS

Component providers must provide the following in order for the component to be validated by Intel. Developers submitting components may be required to provide additional information as Intel deems necessary in order to offer components for use.

NOTE - In the case the submitted component is Open Source, the developer is expected to upload the source code/project for that component. Because it is not required for an Open Source component to incorporate the IADP SDK, the requirement for uploading the component library binaries compiled and built with debug and production GUID is not required.

5. COMPONENT VALIDATION CRITERIA

In order for a component to pass validation, it must successfully meet pre-defined validation criteria. If one or more of the validation criteria are not met, the component will fail validation. Note that component validation criteria described in this section have been developed by Intel and may or may not align with industry-standard validation tests. At this time, components for Windows*-based applications are accepted.

GEN01 - Component Manifest Criteria

Components submitted to Intel must be packaged as a zip file and should contain the following mandatory files. Component submitted with any of these items missing from the package will be rejected.

• Component library (compiled and built with debug GUID) This will be used by developers who use the component in their application during development. NOTE - In the case of Open Source components the developers are not required to submit this piece.
• Component library (built with production GUID for component obtained after logging into your account in http://appdeveloper.intel.com). This will be used by developers who use the component in their application and submitting it to the Application store. NOTE - In the case of Open Source components the developers are not required to submit this piece.
• Component Test Application (built with Production Application GUID obtained after logging into your account in http://appdeveloper.intel.com). NOTE: This application needs to explicitly incorporate component library built with production GUID for component. This application will be used by the validation team for purely testing only is not part package after it is published on the developer catalog after successful validation. The expectation is that this test application will exercise the APIs exposed by the component. This test application should contain all the files required for it to run on the system. The developer may optionally package this as an MSI package. NOTE: In the case of Open Source, it is not mandatory to incorporate the IADP SDK, therefore it is test application can be the same as the demo application explained below.
• Documentation regarding the component. Clear and detailed documentation which describes the interfaces, parameters with code snippets, functional and non-functional behavior, conditions and dependencies for using the component. At this point we only support documentation in the English language.

Additional optional items:

• Demo Application to demonstrate the features of the component (Built with no integration with the IADP SDK). This application is purely to demonstrate the component features so an application developer can get a firsthand experience of how the component can be used. In order that an application developer run the Demo Application without purchasing the app, the component developer must not integrate the IADP-SDK into the component or app.

INC02 - Objectionable Content

Components that reference or contain any of the following will be rejected:

• Sex / Nudity - Images that are suggestive or sexual (e.g. exposed breasts, bare buttocks, visible genitals, visible sexual touching, explicit sexual language, erections/explicit sexual acts, bondage/SM, erotica).
• Content that generally falls under the category of pornography
• Content that depicts or suggests prostitution
• Any content depicting sexual fetishes
• Any content of a sexual nature depicting children or animals

APPENDIX: INTEL TRADEMARK AND BRAND LIST

BlueMoon, BunnyPeople, Celeron, Celeron Inside, Centrino, Centrino Inside, Cilk, Core Inside, E-GOLD, i960, Intel, the Intel logo, Intel AppUp, Intel Atom, Intel Atom Inside, Intel Core, Intel Inside, Intel Insider, the Intel Inside logo, Intel NetBurst, Intel NetMerge, Intel NetStructure, Intel SingleDriver, Intel SpeedStep, Intel Sponsors of Tomorrow., the Intel Sponsors of Tomorrow. logo, Intel StrataFlash, Intel vPro, Intel XScale, InTru, the InTru logo, the InTru Inside logo, InTru soundmark, Itanium, Itanium Inside, MCS, MMX, Moblin, Pentium, Pentium Inside, Puma, skoool, the skoool logo, SMARTi, Sound Mark, The Creators Project, The Journey Inside, Thunderbolt, Ultrabook, vPro Inside, VTune, Xeon, Xeon Inside, X-GOLD, XMM, X-PMU and XPOSYS are trademarks of Intel Corporation in the U.S. and/or other countries.

*Other names and brands may be claimed as the property of others.

Microsoft, Windows, and the Windows logo are trademarks, or registered trademarks of Microsoft Corporation in the United States and/or other countries.

Java and all Java based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.

Bluetooth is a trademark owned by its proprietor and used by Intel Corporation under license.

Intel Corporation uses the Palm OS®* Ready mark under license from Palm, Inc.