Application Packaging Requirements Guide

Before packaging your application for submission, be sure you have reviewed the Validation Guidelines. Intel AppUp Developer program validators do not complete regression test on your application. But a validator will check for the requirements defined in the Validation Process , and will check that the installation package meets the following minimum requirements.

Windows Packaging Requirements

• Submit MSI package – submit a standard Windows Installation package in the form of .MSI file. The MSI must include all required collaterals associated with your application. The MSI must be signed before submitting. Please refer article http://appdeveloper.intel.com/en-us/article/signing-msi-files for signing MSI files
• Silent installation – Your application must install without any required input from the user.
• Single executable – Any and all shortcuts must target only one executable. Your installation can automatically add desktop, quick launch, Start menu, and other shortcuts, but they all must target the same executable.
• Shortcut Target field – The Target entry of the Shortcut table must be a valid feature name/foreign key (Identifier data type) in the Feature table. We support only this data type in the Target field. Do Not use square brackets ([ ]) to indicate a formatted string.
• Avoid arguments in links – Formatted string translation is not supported; therefore, any argument will be interpreted as a plain string. Correct: ‘myapp.exe –start_maximized’ Incorrect: ‘myapp.exe –[#customized_param1]’ In the incorrect example, the argument will be taken ‘as is’ and not translated.
• Check for C++ runtime - If your application requires C++ runtime then inside MSI installer you should check if C++ runtime is installed.
• Java Packaging Requirements- Submit a single JAR file that includes the optional Intel AppUp(TM) SDK library jar file, application jar file(s), and an application manifest file. The Intel AppUp(TM) Software Packaging Utility can help creating these Java runnable jar packages.

MeeGo Packaging Requirements

• Include RPM –RPM formats are required for submission. The application must successfully install on MeeGo(RPM).
• Include all required dependencies – If your installation requires dependent packages not provided with MeeGo, your installation package must include them.
• Follow MeeGo packaging guidance – Follow the packaging information on MeeGo . These MeeGo articles cover the target directory structure where files must be installed, provide a packaging tool, and cover other topics.
• Include source packages – If you are distributing under an open source license, you must include a single source package for each of the RPM.

Codecs Packaging Requirements

• If a codec is available in the distro it should be included as part of the app install / packaging.
• If a codec is freely available, it should be included with the app install / packaging.
• If a codec is included in an OEM build (e.g. fluendo in Asus) it does not need to be included for that build.
• If a codec needs to be purchased / licensed then the developer should provide a link and instructions in their product description for the store.

In addition, for validation, Developers will need to supply us with a codec if it is required.

Related Information

• Troubleshooting Application Validation failures
• Packaging MSI with Visual Studio
• Beta Testing Your Application