Marketplace App Metadata Guidelines

Marketplace App Metadata Guidelines are intended to ensure that apps are submitted with important and necessary supporting information. The metadata that you submit with your app will serve both as necessary information for your app's buyers (eg., your contact info) and as promotional assets (eg., description, screenshots, etc.) that can help drive traffic to and downloads of your app!
Required Metadata Description
App Name This is probably the most important branding element of your app, so be creative! Some important things to keep in mind:
  • In some views within the Marketplace, titles of applications longer than 18 characters will be shortened with ellipsis.
  • Titles must not be longer than 50 characters.
  • App title may contain the word "Liferay" to describe its use or intent as long as the name does not imply official certification or validation from Liferay, Inc. (For example, names such as "Exchange Connector for Liferay" or "Integration Connector Kit for Liferay" would be allowed, while "Liferay Mail Portlet," "Liferay Management Console," or "Liferay UI Kit" would not be permissible without explicit approval). Please refer to our trademark policy for details.
  • Please try to conform the app name, as closely as possible, to the actual plugin (portlet, hook, theme, etc.) name
Support Information

Please include an email address, contact information, and/or website URL for the "Support" field. If someone encounters an issue with your app, they will need a way to contact you.

Even if you choose not to offer Support Services (by unchecking "Offer Support" during the app submission process), we require that you provide support contact information so that buyers can reach you with general questions about your app.

Description Please provide a description for your app in English. At a minimum, the description should provide a concise overview of what the app does. Great descriptions also list key functionalities and what customers can expect to gain by deploying your app. If you'd like to see an example, you can check out our description of Social Office.

It's important that you specify any plugin dependencies (eg., plugins that must be installed prior to running your app) and environment compatibilities (eg., compatibility with specific app servers) here, so that both potential buyers and the Liferay app review team will be aware of these requirements.

Compatibility with Future Minor Releases of Liferay Portal Please include a "+" at the end of the latest version when specifying version constraints in your liferay-plugin-package.properties file (eg., "liferay-versions=6.1.1+, 6.1.20+"). This will ensure that your app will continue to be deployable to future versions of Liferay within a minor release. If, in the future, you discover your app does NOT work with a particular Liferay version, you can modify the list to exclude that version.
Increase Your Potential User Base In most cases, an app that is compatible with CE portal will also run under EE portal, and vice versa. Specifying compatibility with both EE and CE versions of the portal will ensure that a wider audience has access to your app!

You can request a Liferay EE Developer License to support testing and confirm compatibility.
Icon Icons for your app must be exactly 90 pixels in both height and width and must be in PNG, JPG, or GIF format. The image size cannot exceed 512kb. Animated images are prohibited.

The use of the Liferay logo, including any permitted alternate versions of the Liferay logo, is permitted only with Liferay's explicit approval. Please refer to our trademark policy for details.
Screenshots Screenshots for your app must not exceed 1080 pixels in width x 678 pixels in height and must be in the JPG format. The file size of each screenshot must not exceed 384KB. Each screenshot should preferably be the same size (each will be automatically scaled to match the aspect ratio of the above dimensions), and it is preferable if they are named sequentially, for example fluffy-puppies-01.png, fluffy-puppies-02.png, and so on.
Additional Requirements for Themes/Site Templates
 
A theme without content is like an empty house. If you're trying to sell an empty house, it may be difficult for prospective buyers to see its full beauty. However, staging the house with some furniture and decorations helps prospective buyers imagine what the house might look like with their belongings. Liferay's resources importer application is a tool that allows a theme developer to have files and web content automatically imported into the portal when a theme is deployed.
 
All standalone themes that are uploaded to Liferay Marketplace must use the resources importer to include files/web content to provide a sample context for their theme. This ensures a uniform experience for Marketplace users: a user can download a theme from Marketplace, install it on their portal, go to Sites or Site Templates in the Control Panel and immediately see their new theme in action. You can read more about themes and even find examples in the Developer's Guide.