Version 2.1
Last updated April 10, 2013

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
• 2.4 Application Submission Information
• 2.5 Hardware Shipping for Validation

3. Application Validation Criteria

Appendix: Intel trademark and brand list
 

1. INTRODUCTION

The Intel AppUp® Developer Program presents an opportunity for developers to create unique and useful applications for netbooks, laptops/PCs, and tablets based on Intel® processors.

Application Stores for the Developer Program will allow end-users to discover, purchase, and download these applications. 

1.1 OVERVIEW AND INTENT

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

In order for an application to pass validation, it must successfully meet pre-defined validation guidelines. An application will not pass validation if one or more of the validation guidelines are not met. Note that application 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® 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.

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.

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.
• Applications that enable self-updating or over-the-air(OTA) updates are typically forbidden. However, Intel will address each app as a case by case situation. Please contact appup.support@intel.com if you would like your app to be considered.

User privacy/opt-in:

• Applications that collect personal information must contain a privacy policy along with details on how and why personal information is gathered, disclosed, and shared.
• Transmission of personal information is forbidden without explicit user consent (Opt-in) and must be encrypted when transmitting.
• Transmission of information to third parties must also be disclosed to Intel in the “Notes to Validation Team” section of the application submission process.
• Developers who collect personal data will provide the following with their application:
  • Purpose of Collection
  • Notice of transmission
  • Opt-in method to acquire user consent
• 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.
• Examples of personal information or data affected by this guideline
.
• Contacts, phone numbers, photos, audio, video, SMS or other text communication, browsing history, location information and other data stored on mobile devices or data stored in the cloud.

2.3 APPLICATION PACKAGING

Application Packaging

• Packages required are based on OS distribution and checked during installation of the application. Applications must be packaged using these mandatory requirements:
  • Windows* Packaging Requirements
  • Adobe AIR* Packaging Requirements
  • Java* packaging Requirements
  • MeeGo* Packaging Requirements

Mandatory 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

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

Application Keys

• The submitting developer is recommended to submit at least 35 license keys as a comma separated value during app submission. This shall be used by the Intel to validate the application. The keys should be submitted in the following format during app submission:

<"Keys a=5, k=abcd-234d,sk3f-34fk">

Explanation: In the above example, there are 2 unique keys and each key can be used 5 times. This gives a combined total of 10 activations.

Beginning Tag “” are required.

a – enter the number of activations per key

k – actual keys to be entered separated by a comma

<… > – please note the required ” <” and “>” characters in the format.

• To publish an app using keys, the developer must also upload a formatted CSV file in the “Application Keys” drop down menu of “My Dashboard”. There must be at least 1 key uploaded for an app to be published. 

2.5 HARDWARE SHIPPING FOR VALIDATION

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.

• Prior to submitting your application, please contact iadp-validation@intel.com for shipping instructions and inquiries. Please include application name, version number, submission date, company name, contact email and phone number
• 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.
• 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® center

• Applications that do not install and run correctly on the target device will be rejected

ILU02 - Application must uninstall cleanly

• Application must able to uninstall[Either through programs menu or Add/Remove programs]
• 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.
• Desktop, Start Menu, and Program Folder files must be removed. Users must consent to leaving behind any files associated with the application (such as user data, game saves, or setup information).

ILU03 - Application should launch on target device

• Applications that do not launch on the target device will be rejected
• Applications that can ONLY be launched from the application install folder through Windows Explorer will be rejected. There must be either a desktop icon or program menu shortcut. 
• Applications that crash or have errors will be rejected
• Applications that do not function as expected will be rejected
• When error messages regarding launch are displayed to end users, the Intel AppUp® client should be referred to as "Intel AppUp® 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

INC03 - Advertisements and payment mechanisms

• Applications may not encourage users to upgrade or purchase their applications or other applications outside of the Intel AppUp® center. Examples:
• Purchase links, buttons, or images which direct users to purchase or download apps or versions of apps that are listed in the Intel Store, outside of the Intel AppUp center are forbidden.
• Homepage links, buttons, or images directing users to a web site or sites containing applications that are listed in the Intel Store for download and/or purchase are forbidden.
• Installers that download extra files/content that are required for the application to install as part of the install process are allowed.
•  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 2013:
  • 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 hosting content on 3rd party services must utilize the Intel AppUp® SDK.
  • Applications that use this exception will be allowed to use external monetization until December 2013

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. If app is designed for both Landscape and Portrait, the buttons, menus, images must be visible in both layouts.

Sample Devices:

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.
• To publish an app using keys, the developer must also upload a formatted CSV file in the “Application Keys” drop down menu of “My Dashboard”.

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.

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.