---
title: "Publishing an Application to the Tabidoo Public Marketplace"
url: "https://help.tabidoo.cloud/en/article/publishing-an-application-to-the-tabidoo-public-marketplace"
language: "en"
last_updated: "2025-12-31T13:50:24.085Z"
---

# Publishing an Application to the Tabidoo Public Marketplace

Tabidoo allows you to publish applications either as private or public templates. This guide describes the recommended process and requirements for publishing applications to the Tabidoo Public Marketplace, where they become available to all users.

## **1\. Selecting a Public Template**

When publishing your application, select **Public application**.  
This makes the application visible in the public templates and available for other Tabidoo users to install.

* * *

## **2\. Restriction Settings**

For public applications, you can configure the following restrictions:

-   **Auto-update** – users automatically receive new versions of the application
-   **Application lock** – prevents structural modifications to the application
-   **Deny re-publish** – prevents further redistribution of the application

All restriction settings are fully up to the application author.  
👉 **From Tabidoo’s perspective, we strongly recommend enabling Auto-update** to allow ongoing improvements and updates.

* * *

## **3\. Pricing Model**

The application author proposes the pricing model:

-   **Free**
-   **One-time payment**
-   **Monthly subscription**

The selected pricing model will be **reviewed and discussed with the Tabidoo team**.

* * *

## **4\. Application Category**

Select the most appropriate **category** for your application.  
Proper categorization helps users discover your application more easily in the Marketplace.

* * *

## **5\. Application Information**

Every public application must include:

-   **Headline** – a short, clear, and descriptive title
-   **Application description** – what the application does and what value it provides
-   **Screenshots** – ideally taken from real usage scenarios
-   **Live preview** (if available) – highly appreciated

The presentation style of the application is entirely up to the author.

* * *

## **6\. Tabidoo Review Process**

### **6.1 Application Icon**

To maintain a consistent visual style across the Marketplace, the **final application icon is prepared by the Tabidoo design team**, in cooperation with the application author.

* * *

### **6.2 Application Quality and Clarity**

The application should be:

-   clear and easy to understand
-   populated with **example records** (fully filled, not partially completed)
-   for applications working with people (e.g. Contacts), **profile images are recommended**

* * *

### **6.3 Multilingual Applications and Scripting**

-   Field and table names must be **language-consistent** (this is strictly reviewed)
-   Internal names used in scripts should be **in English**

If the application contains scripts or custom scripts, they **must be properly commented**.  
Comments should clearly explain:

-   what the script does,
-   why it is needed,
-   and any non-obvious logic or important dependencies.

This is required to ensure maintainability, easier review, and better understanding for other users and Tabidoo reviewers.

* * *

### **6.4 Application Structure**

-   Group tables into **logical modules**
-   For complex workflows, roles, or scripts, provide a **short and clear explanation** of their purpose

* * *

## **7\. User Onboarding (Key Requirement)**

A user who installs the application should be able to **understand and start using it without external assistance**.

We strongly recommend:

-   creating **application documentation**
-   adding **instructional videos**
-   using a **free HTML dashboard** as a central place for:
    -   application onboarding
    -   release notes and new features
    -   important application-related information

👉 Proper onboarding saves time for both the application author and the end users.

**A significant added value** is:

-   an interactive application tour
-   onboarding tools such as **Product Fruits** or similar solutions

* * *

## **8\. Author Contact and Responsibility**

The application should include a **contact to the author or support** (ideally in the documentation section), where users can ask questions regarding application functionality.

**Note:**  
The application author is fully responsible for the application’s functionality, logic, and content.  
Tabidoo provides the platform for running and distributing applications but does not take responsibility for the specific functionality or content of individual applications.

* * *

Following these guidelines helps us maintain a **high-quality, consistent, and user-friendly Public Marketplace**, while significantly reducing onboarding time for both authors and users.