How to Submit an Application
Introduction
This article provides guidelines for the developer on the application submission process. Instructions are included for all types of applications supported by the Intel AppUp(SM) Developer Program. Developers are encouraged to read the specific sections for more detailed instructions. For component submission, see How to submit a component.
Developer To-Dos before application submission:
Application-Type agnostic steps:
- Get an ID and join the Intel AppUp(SM) Developer Program. (See How to join the Intel AppUp(SM) Developer Program )
- Provide payment information for your organization if you wish to earn revenue from your applications.
- Generate a GUID for your application through My Dashboard -> Start a New Application. This GUID must be used in the code if integrating the AppUp SDK (currently, this is optional). Follow the instructions on how to use My-Dashboard.
- Integrate the AppUp SDK in your application. This is optional, but highly recommended and provides DRM capabilities.
- Compiled a binary for submission (see How to Develop an Application and the Developer Guidelines for details; review the Application Packaging Requirements Guide for the packaging requirements).
Application-Type specific steps:
-
Windows Native/.NET application submission:
- Download and integrate the latest AppUp SDK. Separate SDKs are available for C/C++ apps and .NET apps. Integrating the AppUp SDK is optional but highly recommended.
- Develop and package your application as an MSI installer . Alternatively, is using the SDK, follow this process to create and MSI installer
- Get your MSI digitally signed from an approved Certificate Authority. Self signed applications will not pass validation. Follow the Process to sign MSI files
-
Java* Submission
- If using the SDK, follow and complete the Packaging process for Java* SDK
- Download and integrate the latest AppUp™ Java* SDK into your Java* application. This is optional but highly recommended.
- Develop your app for Oracle Java* runtime 1.6 or greater.
- Package your app as a jar file.
- Get your JAR file digitally signed with an approved Certificate Authority (self-signed applications will not pass validation). Signing JAR files article provides more details.
-
Adobe AIR* Submission
- If using the SDK, follow and complete the Packaging process for Adobe AIR* SDK
- Download and integrate the latest Adobe AIR* SDK into your application. This is optional but highly recommended.
- Develop your app for Adobe AIR* runtime 1.5.3 or greater.
- Get your application digitally signed with an approved Certificate Authority (self-signed applications will not pass validation)
-
MeeGo Submission
- If using the SDK, follow and complete the Packaging and Compliance guidelines for MeeGo* Applications
- Download and integrate the latest MeeGo* Intel AppUp™ SDK into your application. This is optional but highly recommended.
- Package your app as an RPM file.
- Code signing is not required for MeeGo apps.
Also, download and review the Application Submission Checklist and Application Readiness Checklist before continuing. To simplify application submission, make sure you have completed all items on the checklists before submitting your application.
Application Submission Overview
To submit an application, you must login to your account on the Intel AppUp(SM) Developer Program web site and click “My Dashboard” in the upper-right corner of the window. Application submission consists of several steps in which the Intel AppUp(SM) Developer Program web site gathers necessary information to validate and publish your application for distribution. The steps include the following:
- Application Info – gathering your publisher name and application information such as screenshots, icons, languages, and descriptions.
- Pricing – set the price for you app or make it free.
- AppUp Center – where you can add people to beta test your app.
- Upload Info – upload your msi, jar, rpm, air, etc file into your account
- Validation – You can add hardware and software testing requirements for the validation team.
- Overview – where you can review all your information and submit your application for validation.
Keep in mind that the following rules for application submission apply:
- Do not use your browser buttons to navigate the submission pages.
- You follow the steps sequentially. You can go back to any completed step simply by clicking on the navigation at the top of the page. You can move forward to any step you have already completed. You cannot move to a step you have not completed.
- Once you complete the Store Info step, and at any step up to Submit, you can save your application information for editing later through the Dashboard (see How to Use My Dashboard).
- Once you submit your application, it stays in the validation queue until validation starts. You can remove it from the queue and edit it through your Dashboard until validation starts.
- Once validation starts, you cannot edit application information until the validation process completes and the validation engineer has either rejected or approved your application.
Submitting Your Application
Application Info and Pricing:
- Use the Current Organization drop-down menu to select the organization this application will be published under. Any payments for sales of the application are made to this organization.
- Click on “Start a New Application” and enter the application name. This is the name that appears in the App Store. It must be a unique name for the entire App Store. If the application name you entered is not unique, a message appears. You will have to rename your application before continuing. A GUID is created along with the Application Name.
- Enter the name you will publish this application under.
The Publisher Name appears in the App Store; it must be a unique name in the system. The Publisher Name can be the same as the organization or another name, but the site does not allow identical Publisher Names.
This name will be associated with the Organization. If you select this Organization the next time you submit an application, the site will automatically select this Publisher Name. You can, however, change the publisher name.
- Now enter all the application specific information. You can either Save the entries and return to them later or click Next to upload information in the other tabs.
Uploading the application binary:
To help ensure a successful validation, review the Application Packaging Requirements Guide, and make sure all the requirements in the Application Readiness Checklist are completed before uploading.
Your application must comply with any export restrictions. If you use encryption in your application, be sure to click through the questions under Export Compliance. You might need to submit a CCATS; have it ready to upload, if necessary.
- Click Upload and select your binary to submit. If your application is open source, you must package and upload both a binary and the source files. See the Application Packaging Requirements Guide.
- Add any notes you consider important to the validation engineer regarding the file you are uploading. For example, if you are uploading a new version of an application that failed validation, you can note what you fixed in your application. This information is not published to the App Store.
- Click Save to save your application information to edit later, or click Next to continue.
Submitting the application:
- Before clicking the Submit button, verify all the information you’ve entered is accurate. You can edit the information or navigate to a previous page to correct any entries.
- If you want to invite beta testers to test your application, enter their emails and names here. They will be invited to test your application.
- Click Submit to submit your application for validation.
Submission Fields and what they mean:
Below is a summary of the fields in the submission process based on their purpose:
Store Info
|
Field |
Description |
Required |
|
Application Name |
The name is automatically populated from the name you entered to create the application. You can change it here, but it must be a unique name to the App Store. You cannot edit the GUID. |
|
|
Version |
This number appears with the application name in the App Store, e.g. My Application Version 7.2.5. It is always good practice to include a Version number to help customers identify the version they are using. You should also update your Version number whenever you submit a new application binary for an already published application. Neither the site nor the validation process refers to this Version number for internal processing. The site generates its own, non-public versioning for internal processing and for reference any time you upload a new component binary. (If you do not upload a new binary, the internal version does not change.) After publishing your application, if you upload a new binary, the site will notify customers. It is good practice for you to include a Version number and change it whenever you upload a new binary. |
|
|
Product Icon |
Your icon file to be used in the App Store and in the application. Use the Upload button to select the file. It must be of the type and size specified: at least 100x100 pixels (1:1 aspect ratio) in .png format only. See the Developer Guidelines, the Application Readiness Checklist, and the Intel AppUpSM Developer Program Application Submission Validation Requirements document. |
|
|
Tagline |
Enter a very short, promotional statement of your application for the App Store. |
|
|
Date to Make Available |
The target date you would like the application released. Enter in date format (mm/dd/yyyy), or use the calendar tool next to the entry field. Intel does not guarantee release by this date |
|
|
Short Description |
Enter a short description for the App Store (300 characters maximum). |
|
|
Full Description |
Enter a longer description for the App Store to display more details when requested (5000 characters maximum). |
|
|
Feature List |
Enter a short feature description, highlighting an application feature/benefit, which will be included with your Full Description. Click ‘+’ to add another feature; click ‘X’ to delete a listed feature. The feature list appears as a bulleted list in the App Store. |
|
|
Primary Category/ Secondary Category |
Select a primary category (required) and secondary category (optional) from the drop-down menus. |
|
|
Tags |
Enter keywords the App Store can use during a search. |
|
|
Primary screenshot |
Use the Upload button to select your primary screenshot file to be used in the App Store. It must be of the size specified |
|
|
Additional screenshots |
Add up to two more screenshots of the specified size. |
|
|
Release Notes |
Enter a URL where developers can view the release notes for your component. |
|
Support
|
Field |
Description |
Required |
|
Supported OS Platforms |
Select the operating system(s) your application runs under (shift-click or control-click to select multiple operating systems) |
|
|
Target Device Capabilities |
Select the devices your application supports (shift-click or control-click to select multiple devices) |
|
|
Supported Runtime |
Select the runtime(s) your application supports (shift-click or control-click to select multiple runtimes) |
Y/N |
|
Support Email |
Enter a valid e-mail address where support queries can be sent. The e-mail address is not published to the App Store. It is used to relay queries sent by customers regarding your application. This field is validated for correct e-mail format. |
|
|
Support URL |
Enter a web URL where consumers can find support information. |
|
|
Open Source? |
If your component is not offered under an open source license, click ‘No’. Then select whether to use the Intel default End User License Agreement (EULA), or to enter your own EULA. If you select your own, a text box opens, allowing you to enter your license agreement. If your component is offered under an open sources license, click Yes, then check which agreement(s) it is offered under. |
|
Pricing & Components
|
Field |
Description |
Required |
|
Components Used |
Add any components you’ve used by clicking Add/Edit Components. In the pop-up window that appears, check the box next to the component’s name. You can add multiple components at once. The component(s) you select are listed on this page, along with the published Revenue Share the component developer requests. If the developer will negotiate a Revenue Share, you can click counterbid and submit your offering. Your component(s) Revenue Share must not exceed 100%. |
|
|
Sales Price |
Select Free or Paid, depending on your offering. |
|
|
Select a currency and price |
This information will automatically populate the pricing tables that follow in appropriate currencies. You can change the pricing in these tables. Use a currency you are familiar with to view how your familiar price will convert to other currencies. |
|
|
Pricing/Countries |
You can change your price offered in each currency. Select the countries you want your application sold in. The pricing tables show you how much of your price will go to Revenue Share components, and it will calculate your net earning from the application after applicable taxes and the Program’s share. |
|
|
Add New Countries |
Check the box if you want to automatically sell your application to any new countries as they are added to the list of countries in each currency. |
|
|
New Currencies |
Check the box if you want to be notified when new currencies are added to the Program. Your application will not automatically be sold under a new currency without your approval. |
|
Validation
Your application is validated against the requirements summarized in the Developer Guidelines, and defined in the Intel AppUp(SM) Developer Program Application/Component Suitability and Validation Guidelines document.
Until actual validation starts, you can remove the application from the validation queue and edit it, including uploading a new binary. The site prevents changes once validation starts
If you upload a new binary, an internal versioning system will assign it a new version for validation and release. You can retain the version number you enter, or update it. Your version number is the only version published with the application.
You should periodically check "My Dashboard" for the results of validation. The Dashboard displays the date it is published.
If your application fails validation, information appears on the Applications page, indicating why it failed. The article Where are my validation results? provides details on how to read the validation report.
Comments
"Primary screenshot: Use the Upload button to select your primary screenshot file to be used in the App Store. It must be of the size specified"
what size should screenshots be? size should be specified here, right?
Hi Kusuma,
You will get a notification before it is published or rejected. is there any specific app which you are trying to look up.
Thanks
Amar
After passing validation will the developer get any notification asking for further proceedings or it is directly published in the store?
Hello Tony John,
The app will be available almost immediately after publishing.
Regards
Hal G.
Technical Support Team
Intel AppUp(SM) Developer Program
Intel AppUp(SM) center
*Other names and brands may be claimed as the property of others.
What happens after the app gets published. Will it be available to users immediately. Or the developer has to make it live?
Hi Guys,
This great info, regarding submission of apps. Go through it. Very useful.
Rgds,
Sachin Panchal
HI friends
i will be working on some audio post processing algorithm optimization on Intel atom, all kind of a and assembly optimization done, now i want to do cache optimzation how can i do do this cache optimization could you elaborate me.?