How to Submit a Component
This How-to guides you through the component submission process. For application submission, see the How to Submit an Application.
Before Starting Component Submission
Before you submit a component, you must have completed the following:
- Received an ID and joined the Intel AppUp(SM) Developer Program (see How to Join the Intel AppUp Developer Program).
- Provided payment information for your organization if you want to earn revenue from your components. [1]
- Generated a GUID for your component; you can generate a GUID during the submission process, but the GUID must be used in your code if you're using the SDK (optional).
- Have a compiled binary for submission (see Application/Component Suitability and Validation Guidelines and the Developer Guidelines for details). The binary must include API user documentation and licensing information. It is recommended you review the component samples and documentation which are part of the IADP SDK
Also, print and review the Component Submission Checklist before continuing. To simplify component submission, make sure you have completed all items on the checklist before submitting your component.
Component Submission Overview
Component submission consists of several steps in which the Intel AppUp Developer Program web site gathers necessary information to validate and publish your component in the Developer Catalog. The steps include the following:
- Organization – gathering your organization and publisher names.
- Catalog Info – gathering information about your component that appears in the Developer Catalog; a GUID can be generated at this step if you don’t have one.
- Support – gathering information that will be used to support your component.
- Pricing – setting your component Revenue Share.
- Upload – where you choose the binary to upload.
- Submit – where you can review all your information and submit your component for validation.
Keep in mind that the following guidelines for component submission apply:
- Do not use your browser buttons to navigate the submission steps.
- 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 go forward to any step you have already completed. You cannot go to a step you have not completed.
- Once you complete the Catalog Info step, and at any step afterward up to Submit, you can save your component information for editing later through the Dashboard (see How to Use My Dashboard).
- Once you submit your component, it stays in the validation queue until validation starts. You can still remove it from the queue and edit component information through your Dashboard until validation starts.
- Once validation starts, you cannot edit component information until the validation process has completed and the validation engineer has either rejected or approved your component.
Submitting Your Component
- Use the Current Organization drop-down menu to select your organization under which the component will be published.
Any payments for use of the component are made to this organization. - Enter the component name.
This is the name that appears in the Developer Catalog. It must be a unique component name for the entire Developer Catalog. - Click Get a GUID or Submit Component.
When you click Get a GUID, the system generates a GUID and automatically saves the component and GUID in your list of components. You can edit the component and submit it at any time.
When you click Submit Component, you start the submission process and proceed to the Organization step.
If the component name you entered is not unique, a message appears. You will have to rename your component before continuing
Organization
- Organization: Enter the name of the organization that has been registered with the developer program and is the legal entity which will be the distributor for this component. NOTE – This designated organization cannot be changed after the application is changed.
Publisher Name: This is the name which will be visible to customers viewing your component in the developers catalog. For example, ACME Americas LLC” could be your legal name, while ACME name is used for the publisher.
This name will be associated with the Organization. If you select this Organization the next time you submit a component, the site will automatically select this Publisher Name. You can, however, change the publisher name. - Click Next.
Catalog Info
Enter the catalog information
|
Field |
Description |
Required |
| Component Name |
The name is automatically populated from the name you entered to create the component. You can change it here, but it must be a unique name to the entire Developer Catalog. This is the name of the component that is displayed in the developer catalog. NOTE – The component name cannot be changed after it is published.. |
|
| Version |
This number appears with the component name in the Developer Catalog, e.g. My Component Version 7.2.5. It is always good practice to include a Version number to help developers identify the version they are using. You should also update your Version number whenever you submit a new component binary for an already published component. Neither the site nor the validation process refers to this Version number for internal processing. The site generates its own, non-public versioning identification 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 component, 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. |
|
|
GUID |
You cannot edit the GUID. |
|
| Product Icon |
Your icon file to be used in the Developer Catalog and in the component. Use the Upload button to select the file. It must be of the type and size specified(120x120 pixels). It must be .gif,.jpg or .png file. See the Developer Guidelines, the Component Readiness Checklist, and the Intel AppUp Developer Program Application/Component Submission Validation Requirements document. |
|
| Tagline |
Enter a very short, promotional statement of your component for the Developer Catalog.This tagline should describe the component’s core functionality to interested developers. |
|
| Start/End Dates |
The target date you would like the component 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. End Date is the date when your component will automatically be unpublished from the developer’s catalog |
|
| Short Description |
Enter a short description for the Developer Catalog (300 characters maximum). This short description will display in search results and whenever your component is listed. Include keywords that will help developers see core features of your component at a glance. |
|
| Full Description |
Enter a longer description for the Developer Catalog to display more details when requested (5000 characters maximum). This is a detailed description of your component describing core features, usage and functionality. Please include any special system requirements, capabilities, or benefits your would like a developer to understand before using your component. |
|
| Feature List |
Enter a short feature description, highlighting 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 Developer Catalog. |
|
| Primary Category/ Secondary Category |
Select a primary category (required) and secondary category (optional) from the drop-down menus. |
|
| Tags |
Enter keywords the Developer Catalog can use during a search. Use words that describe the core functions of your component and not category name.. |
|
| Primary Screenshot |
Use the Upload button to select your primary screenshot file to be used in the Developer Catalog. It must be of the size specified. A screenshot depicting your component used in an application is recommended visual for developers. It must be in .gif,.jpg,.png file. |
|
| Additional Screenshots |
Add up to two more screenshots of the specified size. After selecting the file, click the Upload button to continue. |
|
| Development Language |
Select the development language.This is the primary development language used to build and compile your component. This is to help interested developers understand the code and compatibility and/or any constraints on using your component Shift-click or control-click to select multiple languages. |
|
| Component Technologies |
Select technologies you used in your component, such as Active X,* Meego* Runtime, Flash, Java, etc. Shift-click or control-click to select multiple languages. |
|
| Release Notes |
Enter a URL where developers can view the release notes for your component. |
|
| Resource Links |
Enter a short description of additional topics relative to your component and the URL where developers can find the information, such as FAQs, API user documentation, sample code, blogs, etc.). |
|
Click Save to save your component information to edit later, or click Next to continue.
Support
Fill in the support information.
|
Field |
Description |
Required |
| Supported OS Platforms |
Select the operating system(s) your component supports (shift-click or control-click to select multiple operating systems) |
|
| Supported Runtime |
Select the runtime(s) your component supports (shift-click or control-click to select multiple runtimes) |
|
| Support Email |
Enter a valid e-mail address where support queries can be sent. The e-mail address is not published to the Developer Catalog. It is used to relay queries sent to the Catalog regarding your component. 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. |
|
| Component License Agreement |
Select the Intel Default License Agreement or provide your own agreement in accordance with the minimum requirements stipulated in the submission and distribution agreement |
|
Click Save to save your component information to edit later, or click Next to continue.
Pricing
Select whether your component is distributed for Free or non-free.
|
Field |
Description |
Required |
| Distribution Method |
Free components do not earn you revenue. Paid components earn you revenue. All components offered under an open source license are Free. |
|
| Revenue Share |
Revenue Share is the percentage you require of the sale price for any application in which your component is used. For example, if you set your Revenue Share to 12%, a $10 application would pay you $1.20. Your share will be paid net of any applicable withholding taxes. |
|
| Allowed in free applications? |
You can choose to allow your component to be used for free in Free applications. |
|
Click Save to save your component information to edit later, or click Next to continue.
Upload
To help ensure a successful validation, make sure all the requirements in the Component Readiness Checklist are completed before uploading. Make sure the binary includes your API user documentation and licensing information. Components without these items will automatically be rejected.
Your component 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.
- Add any notes you consider important to the validation engineer regarding the file you are uploading.
2.
For example, if you are uploading a new version of a component that failed validation, you can note what you fixed in your component. This information is not published to the Developer
Catalog.
- Click Save to save your component information to edit later, or click Next to continue.
Submit
- Before clicking the Submit button, verify all the information you entered is accurate. You can edit the information, or navigate to a previous page to correct any entries.
- Click Submit to submit your component for validation.
Validation
Your component is validated against the requirements summarized in the Developer Guidelines, and defined in the Intel AppUp Developer Program Application/Component Suitability Guidelines and Validation Criteria document.
Until actual validation starts, you can remove the component 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 component. However, uploading a new binary for an already published component triggers the Developer Catalog to indicate a new version of your component is available, when it passes validation.
You should periodically check your Dashboard (Components page) for the results of validation. The Dashboard displays the date it is released and published to the Developer Catalog.
If your component fails validation, information appears on Your Components page, indicating why it failed. Consult the Intel AppUp Developer Program Application/Component Suitability Guidelines and Validation Criteria document for error codes and recommended solutions.
Comments
Hi All,
I am going to develop component now onwards so this is very useful for me on submission of it.
Rgds
Sachin Panchal