Requirements Checklist
Apps must meet the following criteria in order to be publicly listed on the AppExchange. For a more detailed description of what we look at during the review process, see Preparing for Review.
Note: Beginning March 15, certification is required for all commercial apps published on the AppExchange. For details on the certification program, visit the Certifying Your App page. To get started with the certification process, complete the partner inquiry form.
- Contains app title and version, abstract, and description
- Lists the salesforce.com editions with which the application is compatible
- Includes app logo, screenshot and thumbnail graphics, as well as a Test Drive demo user name and password
- Provides pricing information and, in the case of commercial applications, sales contacts and a licensing agreement
- Correctly states all editions the app will work in, including any specific feature requirements
- Works in all salesforce.com instances — applications that hardcode links to specific database environments (for example, by using URLs, such as https://emea.salesforce.com/) will fail this test and be rejected
- Fully and accurately documents the installation process if any special configuration or setup steps are required
- Solicits and stores salesforce.com user credentials (usernames and passwords) only if the app has been reviewed and certified by the salesforce.com certification team. Certification is a paid program. Click here for more information.
Native Application
- Has been packaged as a "managed package" before being uploaded, as explained in the Packaging & Upgrading section on the Apex wiki
Composite Application
- Clearly identifies publisher-owned or widely recognized external services used
- Represents a true integration with the Apex platform (not just external service data displayed in a custom tab)
- Uses https wherever password or session information is passed
- Has been packaged as a "managed package" before being uploaded, as explained in the Packaging & Upgrading section on the Apex wiki
Client Application
- Clearly specifies operating system and applications requirements
- Represents a true integration with the Apex platform (not just external service data displayed in a custom app or window)
- Provides "meaningful" interaction with the Apex platform (interacts with the customer's Salesforce data)
- Is not a Developer Edition account with a packaged app manually
installed in it — but instead has been created during the packaging process by clicking the Create
Test Drive button that appears after the package has been uploaded to the AppExchange
NOTE: If the package being provided is an extension to an existing app, the developer must first manually install the base app and then install the extension app into the Test Drive organization. - Includes an adequate amount of data
- All relevant objects and tabs are populated in varying states of completeness
- Easily accessed sample reports and dashboards are provided, if appropriate
Test Drive for a Composite Application
- Requires no separate login or password to initiate external access (single sign-on)
- Requires no registration process or customer-specific data to operate
- Should demonstrate the functionality of the app and walk the customer through the integration with salesforce.com
- Should include:
- A brief introduction
- A step-by-step walk through using screenshots that show the entire tab where the function is being performed
- Additional information and a conclusion
- The app's value proposition, not company history or general info about the on-demand proposition
- Can be a multimedia presentation in any of a number of formats, including Acrobat Connect Professional, Flash, static HTML, or PowerPoint.
- Makes all custom installation and configuration steps easily accessible via documentation links on the Overview or About tab within the application
- Uses all display elements consistently
- Provides at least one direct method for contacting support (email, phone, or Web site URL)