Publishing Your App

Bu içerik henüz dilinizde mevcut değil.

When you’re ready to share your app, you can submit your app to the Crowdin Store. Once published, your app will become accessible for installation and usage by other Crowdin users. But before publishing an app, you need to obtain an author account in the Crowdin Store CMS. To do that, contact our customer success service and follow the provided instructions.

Creating Author Page

Every developer that publishes apps on the Crowdin Store will have a personal author page.

Here is an example of the author page: Crowdin.

Once you obtain your author account, you can proceed to your author page creation. To do that, navigate to the Authors collection and click Create New. You’ll need to provide some information for your author page. We recommend doing this before you start the publishing process.

In the table below, you can check out the fields that need to be filled for your author page.

Field	Description	Required
Name	Author’s display name (e.g., a company or developer name).	yes
Slug	The unique author identifier used in the author page URL. Use a descriptive, SEO-friendly keyword in lowercase - no more than 2-3 words. Avoid changing it later, as this breaks existing URLs and references.	yes
Description	A short bio displayed on the author page. Aim for 1-3 sentences.	yes
Email	Author’s contact email. It’s private and visible only to authenticated users.	yes
URL	This can be a link to a business website.	no
Support URL	This can be a link to a support page.	yes
Logo	The Author’s logo. We recommend using a .png image with a transparent background. Ensure the logo would fit nicely into square and circle shapes in the product UI. Recommended size: 400×400 pixels.	yes
Verified	Defines whether the author is verified by the Crowdin Team. Adds the Verified author badge to the Author’s page. Can be set exclusively by the Crowdin Team.	no

When you finish, click Save Draft. Your author page will stay a draft until the Crowdin team reviews and publishes it - see App Review Process. Once the page is published, you can use the Open in Store button in the sidebar to view it on the Crowdin Store.

Preparing App Page

Every app published on the Crowdin Store will have its own app page. This allows other Crowdin users to find and install your app. To start creating an app page, navigate to the Items collection and click Create New. You’ll need to provide some information for your app page. We recommend doing this before you start the publishing process.

The app page fields are organized into several tabs. In the tables below, you can check out the fields that need to be filled for your app page.

Details Tab

Field	Description	Required
Type	The app type. See the complete app type list. Some of the fields below are displayed only for specific app types.	yes
Name	Specify a name for your app. This can be something descriptive or a bit creative. Users can search for your app using this name, but you also have tags to add relevant keywords.	yes
Slug	The unique app identifier used in the app page URL. Use a descriptive, SEO-friendly keyword in lowercase - no more than 2-3 words. Ensure your app slug matches the app identifier in the app’s `manifest.json` file.	yes
Tagline	The tweet-sized app description. Make it an attention grabber.	yes
Logo	The app’s logo. Ensure it fits nicely into square and circle shapes in the product UI. Recommended: a 400×400 pixels .png image with a transparent background.	yes
Author	The app’s author. Select the author created in a previous step.	no
Product	The product compatibility. Defines whether the app is compatible with the specific product. Select carefully. Multiple choices are allowed.	yes
Category	Select the categories your app best fits in. You can select multiple categories.	yes
Tags	Tags allow to group and filter apps by keywords.	yes
Manifest URL	The URL to the app’s `manifest.json` file. Displayed and required only for the App type.	in some cases
Manifest Identifier	Specify your app manifest identifier if your slug is different. Displayed only for the App type.	no
Code	Fill it in with your QA check code. Displayed and required only for the QA Check type.	in some cases
Config	Located in the Advanced section. Additional app page options: Wizard - show the installation wizard, Recommended - mark the app as recommended on the Crowdin Store.	no
Pricing	Located in the Advanced section. Describes the app’s pricing plans displayed on the app page. Leave it empty for a free app. See App Pricing to check out the possible configurations.	no

Content Tab

Field	Description	Required
Content	The app description goes here. Describe how the app works and how Crowdin users can benefit from it. Use between 80-240 words. Markdown syntax is supported. Also, you can add screenshots of your app. See App Description for tips.	yes

Links Tab

Field	Description	Required
URL	The additional external link to resources related to your app. It’s required for the Guide items. Optionally, it can be specified for any other kinds of items.	in some cases
Enterprise URL	Similar to the URL field. The main difference is that this URL will be displayed in the Crowdin Enterprise Store.	in some cases
Resources	Additional links displayed on the app page (e.g., documentation, tutorials). Each resource consists of a URL, a title, and the products it applies to.	no

Marketing Tab

Field	Description	Required
Meta Title	The page title for search engines and social shares (max 60 characters).	no
Meta Description	The summary shown in search results (max 160 characters).	no
Canonical URL	The custom canonical URL for the app’s page.	no
Robots Meta	The robots directive for the app’s page (e.g., `noindex`).	no
CTA Section	Enables the CTA section at the bottom of the item description.	no
Related Apps	Other Crowdin Store items to display as related apps on the app’s page.	no

Besides the tabs, a few options are located in the sidebar of the app page editor:

Field	Description	Required
Beta	Defines the app’s lifecycle status. A beta phase typically begins when the app is feature-complete but likely to contain several known or unknown bugs. Adds a corresponding label on the app’s page.	no
Open in New Tab	A special kind of item on the Crowdin Store that has no own page. It’s just an external link that opens in a new tab. If enabled, a URL is required.	no
Sort	The score for manual ordering. A higher value ranks the item higher. Can be set exclusively by the Crowdin Team.	no

App Types

The app type list:

Type	Description
App	A regular Crowdin Application (e.g., Project Integration, Editor Panel, custom file format, Resources or Reports app). Should have Manifest.
Guide	The item that describes some integration or functionality. Usually, it has an external link.
QA Check	The custom QA Check. Only available in Crowdin Enterprise. To see the examples, visit the QA Check section on the Crowdin Store.
System	The native Crowdin Integration or file extension.

App Description

The Content field is crucial for helping users understand your app’s value. Here are some tips for creating compelling app descriptions that convert visitors into users.

Structure Your Content

A well-structured description helps users quickly understand what your app does:

Lead with value - Start with the main benefit your app provides
Explain how it works - Describe the key features and workflow
Include use cases - Help users envision how they’d use your app
Add visuals - Screenshots make your app more tangible

Using Admonitions

You can use admonitions to highlight important information in your app description. The following admonition types are supported:

:::note
Use notes to provide additional context or clarify important details about your app's functionality.
:::

:::tip[Pro Tip]
Tips are great for sharing best practices or suggesting optimal ways to use your app.
:::

:::info
Use info blocks to highlight key features or compatibility information.
:::

:::warning
Warnings help users understand limitations, prerequisites, or potential issues they should be aware of before installation.
:::

:::danger
Use danger admonitions sparingly to highlight critical information, such as actions that cannot be undone or potential data loss scenarios.
:::

App Pricing

The Pricing field (Details tab → Advanced) describes the app’s pricing plans. It is used only for rendering pricing info on an app page. You should also implement the behavior in your app.

Read more about Crowdin Apps Monetization.

If your app is free, just leave the Pricing list empty. If your app is paid, click Add Plan and configure the plan using the following fields:

Field	Description
Plan Type	The type of app’s plan. Possible values: Recurring and Free.
Price	The price of the app for recurring plans. Specify the Monthly or/and Yearly cost and select the currency (USD or EUR).
Free Trial	Defines if the application has a trial period. By default it’s 14 days for crowdin.com and 30 days for Crowdin Enterprise.

App Review Process

The application needs to go through the review process before Crowdin can list it on the Crowdin Store. The review process includes reviewing the author’s and app’s descriptions on the respective pages on the Crowdin Store.

The review is built into the publishing workflow:

New author and app pages are always saved as drafts. A draft is visible only to you and the Crowdin team - it doesn’t appear on the Crowdin Store.
The Crowdin team reviews your page and publishes it for the first time.
After the first publish, your subsequent edits go live immediately - no re-approval is needed.

To take a published page off the Crowdin Store, unpublish it - the page reverts to a draft and is hidden from the Store without being removed, so you can publish it again later.

Author Verification

You can request author verification for your organization. A Verified author badge is a check that appears next to the author account name on the Crowdin Store and means Crowdin has confirmed that an author account is the authentic presence of the company or individual it represents.

To request an author verification, contact our customer success service, and we will agree on the further steps.

Bu sayfa faydalı oldu mu?