You can submit Adobe AIR* applications via the Intel AppUp(SM) Developer Program site. If you are an existing Adobe AIR* developer on the Intel AppUp(SM) Developer Program, please note that packaging Adobe AIR* apps has changed.The Adobe packaging service has migrated to the Intel AppUp Encapsulator tool, thus you can no longer can directly upload an Adobe AIR* file using the app submission form. You will instead use the Intel AppUp Encapsulator tool to generate the MSI and upload the MSI onto the Intel AppUp developer program. See Packaging Comparison Table at end of this article for differences.

Contents

• Step 1: Validation Guidelines
• Step 2: SDK, Signing & Packaging Adobe AIR*
• Step 3: Submitting Adobe AIR* app
• Adobe AIR* for Intel AppUp(SM) Developer Program FAQs
• C++ vs Adobe AIR* Requirements Table

Step 1: Review validation guidelines

Before packaging your application for submission, be sure you have reviewed the Validation Guidelines. Intel AppUp(SM) Developer Program validators do not regression test your application. A validator will check for the requirements defined in the Validation Process, and will check that the installation package meets the following minimum requirements.

Additionally, there are requirements for Adobe AIR* applications that differ slightly from the C++ applications. Review Step 2 to understand these requirements.

Step 2: SDK, Digital Signing & Integrating InMarket* SDK for your Adobe AIR* App

1. SDK: For building an Adobe AIR* application for Intel AppUp you will need to download the appropriate InMarket SDK and integrate the .SWC file. If you have existing Adobe AIR* applications you will need to download InMarket SDK and re-import the .SWC using the appropriate IDE such as Flex Builder or Flash Builder.
   
   Adobe AIR* apps for Intel AppUp must be built using either Flex SDK 3.5a for Adobe AIR* 1.5.3 or Flex SDK 4.1 for Adobe AIR* 2.0/2.5 apps. (Note: Flex SDK 4.0 is not supported).
   
   Although there are other IDE that may work to compile your Adobe AIR* app, Intel recommends you use Flex Builder 3 for Flex SDK 3.5a or Flash Builder* 4 for Flex SDK 4.1 as those are the development environments for which the InMarket SDK has been tested.
   

   Visit the Adobe AIR* Developer Center for more information on Adobe AIR* application development.

   • For Flex SDK 3.5: Please download the InMarket SDK labeled "InMarket_sdk_1.0.0.24_air1.5.3Flex". Make sure you are using Adobe AIR* "1.5.3" namespace in your application descriptor file.
   • For Flex SDK 4.1/Adobe AIR* 2.0: Please download the InMarket SDK labeled "InMarket_sdk_1.0.0.24_air2.0Flex". Make sure you are using Adobe AIR* "2.0" or Adobe AIR* "2.5" (as per your Adobe AIR* SDK) namespace in your application descriptor file.
   
   
   • If you are using Adobe AIR* "1.5.3" namespace in your application descriptor file, then you should download InMarket_sdk_1.0.0.24_air1.5.3Flex.
   • If you are using Adobe AIR* "2.0" or Adobe AIR* "2.5" namespace in your application descriptor file, then you should download InMarket_sdk_1.0.0.24_air2.0Flex.

If you are using Flex Builder or Flash Builder please make sure that you are using a supported Flex SDK with the corresponding Adobe AIR* runtime and InMarket SDK. Intel AppUp supports Adobe AIR* applications created using Flex SDK 3.5 and Flex SDK 4.1.

2. Digital Signing: All Adobe AIR* applications must be converted to an MSI file using the Intel AppUp^TM Encapsulator and digitally signed by one of the following trusted Certification Authorities: Comodo, Go Daddy, ChosenSecurity, GlobalSign, Thawte, TrustCenter or VeriSign. If you have an existing Adobe AIR* application you must get that application signed with one of these authorities. If you submit you application with a self-signed certificate it will be rejected.
3. Integrate InMarket into your Flex Project per the following:

To include the Licensing Manager in your Flex Project:

1. Copy the licensing.swc file to your application's lib folder. You may need to create a lib folder in which case " Your_appplication_Dir/libs" is recommended
2. In Flex Builder select your application in the Flex Navigator pane
3. Invoke the properties dialog by either right-click and select properties or under the Project menu select properties
4. Select 'Flex Build Path'
5. Select the 'Library Path' tab
6. Select the libs folder (e.g. Your_appplication_Dir /libs)
7. Click the 'Add SWC...' button
8. Navigate to licensing.swc click 'OK'
9. Click 'OK' to close the Properties dialog

Steps to Implement the Licensing Manager using Flex Builder or Flash Builder:

1. Open the [Your_appplication_Name] .mxml file in flex builder.
2. In the entry point of your flex based Adobe AIR* application, <mx: WindowedApplication> or
   <s: WindowedApplication> paste in the following code:
   creationComplete = “initApp()”
3. In the Scripts section, paste in the following code:

	import com.adobe.licensing.LicenseManager;

	//Pass in an empty string or NULL. You don't ned to pass the GUID promgramatically.
                //Provide the GUID while packaging it to an MSI using the packaging utility
	private static const MY_UNIQUE_32_HEX_NUM:String = “”;

	//Automatic updates is not supported on Intel AppUp. Set this flag to false
	private static var UPDATE_MODE: Boolean = false;

	//Set this flag to true when in debug mode
	//Set this flag to false when submitting for validation
	private static var DEBUG_MODE: Boolean = false;


	protected function initApp():void
	{
	var licenseManager:LicenseManager = new LicenseManager();
	licenseManager.checkLicense(this, MY_UNIQUE_32_HEX_NUM, UPDATE_MODE, DEBUG_MODE);
	}

1. Finally compile your Adobe AIR* app to create a .AIR file and include your certificate information. This is typically done using the “Export Release Build”.

To include the Licensing Manager in your Flash Professional Project:

1. Open the .fla file for the project
2. Click on File->Publish Settings...
3. Click on the tab entitled 'Flash' in the Publish Settings dialog
4. Click on the 'Settings...' button for the Script field (it should be set to ActionScript 3.0)
5. Click on the 'Library path' tab in the Advanced ActionScript 3.0 Settings dialog
6. Click the button with the plus sign to add the path to the licensing.swc file
7. Click the 'Add SWC...' button
8. Click 'OK' until the change is finally committed

Steps to Implement the Licensing Manager using Flash Pro:

A sample code is as of below

	
package
{
	 
	
	import flash.display.MovieClip;	
	import com.adobe.licensing.LicenseManager;
	
	public class SampleGame extends MovieClip
	{
		//*************************
		// Properties: You can set the myGuid string to Empty or null value as per below
		
		
		private static const myGuid:String="";
		private static var UPDATE_MODE:Boolean=false;
		private static var DEBUG_MODE:Boolean=false;		
		
		
		//*************************
		// Constructor:
		
		public function SampleGame ()
		{
			// Initialization Code
			
			var licenseManager:LicenseManager = new LicenseManager();
			licenseManager.checkLicense( this, myGuid, UPDATE_MODE, DEBUG_MODE );
			
		}
}

Visit the Adobe AIR* Developer Center for specific information on Adobe AIR* application development

Step 3: Submission

After completing the packaging process follow the Submission process for Adobe AIR* applications on the Intel AppUp(SM) Developer Program. Note: The Intel AppUp(SM) Developer Program will accept Adobe AIR* submissions late August, check our Adobe AIR* forum for news.

Adobe AIR* for Intel AppUp(SM) Developer Program FAQs

Q. Do I need an MSI?
A. Yes. You can no longer upload the Adobe AIR* file directly onto Intel AppUp Developer Program. Please upload your Adobe AIR* file and generate an MSI using the Intel AppUp Encapsulator tool and then upload the MSI directly onto the Intel AppUp center.

Q. Can I upload an Adobe AIR* app to Intel AppUp Developer Program today?
A. No, not until the end of September, 2011, when Adobe AIR* apps can be submitted via the Intel AppUp™ Encapsulator Beta tool. That service is undergoing updgrade and will be implemented on The Intel AppUp Developer Program web site by September, 30, 2011.

Q. I am an Adobe InMarket developer and have my application published on Intel AppUp Developer Program through Adobe InMarket. How do I continue to manage the application?
A. If you have published Adobe AIR* applications in the Intel AppUp Developer Program, your account was migrated and login credentials have been sent to you. The login credentials will let you manage your applications directly on the Intel AppUp Developer Program site. Once logged in, analytics for applications published to Intel AppUp Developer Program will be available to you through MyDashboard on the Intel AppUp Developer Program portal.

Q. I am an InMarket developer and I got applications published on InMarket but NOT any on the Intel AppUp Developer Program. Where can I access my account
A. Developers who have Adobe AIR* applications published on Adobe InMarket place but NOT on Intel AppUp Developer Program will have to join the Intel AppUp Developer Program program and create a new ID. They need to package the Adobe AIR* file to an MSI using the Intel AppUp Developer Program Encapsulator tool and then submit the application for validation on the Intel AppUp

Q. I am an InMarket developer and I got applications published on InMarket and also on the Intel AppUp Developer Program . How do I submit binary updates to my Adobe AIR* application
A. Developers can login with the new credentials on Intel AppUp Developer Program portal and if they want to submit an update to their published Adobe AIR* app, they need to package their updated Adobe AIR* app as an MSI using Intel AppUp Developer Program Encapsulator and then need to submit the MSI for validation on the Intel AppUp Developer Program portal. Please be noted that Auto update feature using InMarket licensing call will be rejected in validation.

Q. I am an InMarket developer and I got applications published on InMarket and also on the Intel AppUp Developer Program. How can I update the price of my application (or any meta data like screen shots, application description, price etc.)
A. Developers can login with the new credentials on Intel AppUp Developer Program portal, update the price (or any Meta data), package their updated Adobe AIR* app as an MSI using Intel AppUp Developer Program Encapsulator tool and then need to submit for validation on the Intel AppUp Developer Program portal.

Q. Is Auto update feature supported for my Adobe AIR* application
A. Please be noted that Auto Updates features of the Adobe AIR* application will be rejected in validation. If you got any updates you need to submit the updated MSI again for validation.

Q. Do I need to create a GUID
A. Yes you still need a GUID if you submit your application through the Intel AppUp Developer Program portal. However you do not need to hardcode the GUID anywhere inside your Adobe AIR* application code. You need to provide the GUID to the Intel AppUp Developer Program Encapsulator tool and the tool automatically bundles the GUID along with Adobe AIR* file as an MSI.

Q. Do I need to package or submit Adobe AIR* with my app?
A. Yes. You will need to generate an MSI using the Intel AppUp Developer Program Encapsulator and upload the MSI to Intel AppUp Developer Program portal.

Q. What if my app requires a specific version of Adobe AIR*
A. Your application has to be built with the Adobe AIR* runtime version 1.5.3 or greater. We strongly recommend using the latest Adobe AIR* runtime, version 2.0 or above.

Packaging Comparison Table per Runtime

Read more on packaging requirements for C++ for Windows* and MeeGo*