Marketplace App Requirements
These requirements define the standards for content and presentation of apps published in the Flowlu Marketplace. Non-compliance is grounds for rejecting an app or removing it after publication.
1. App Listing
Required Fields
| # | Field | Requirement |
|---|---|---|
|
1 |
Name |
Clear, descriptive, reflects the app's purpose. No more than 60 characters. Do not use words such as "best", "official", or "by Flowlu" without justification |
|
2 |
Short description |
1–2 sentences describing what the app does. No more than 160 characters |
|
3 |
Full description |
A list of tasks the app solves and features it provides for the user. At least 200 characters |
|
4 |
Icon |
PNG or JPG, square, 256×256 pixels, no transparent background. Do not use third-party trademarks without permission |
|
5 |
Screenshots |
At least 2 screenshots of the app's actual interface. PNG or JPG format, minimum width 1280 pixels. No blur or pixelation |
|
6 |
Category |
Select one of the available Marketplace categories |
|
7 |
Support website or app page |
A valid URL where users can find instructions and get help |
|
8 |
Privacy Policy |
A valid URL of the developer's Privacy Policy |
|
9 |
Requested OAuth Permissions |
Populated automatically from app settings; must match the declared functionality |
Optional Fields
| # | Field | Recommendation |
|---|---|---|
|
1 |
Demo video |
Link to YouTube or Vimeo. Significantly increases install conversion |
|
2 |
Documentation |
Link to detailed documentation or user guide |
|
3 |
Support email |
A dedicated contact for users |
2. Technical Requirements
2.1. The app must launch and function correctly within the Flowlu Portal without console errors that affect functionality.
2.2. The app must not interfere with the Portal interface: it must not intercept events, modify global styles, or block navigation.
2.3. The app must handle OAuth token revocation and server unavailability without freezing the user interface or displaying raw error messages to the user.
2.4. Requested OAuth Permissions must match the declared functionality. Requesting access to data speculatively is prohibited.
2.5. The app must be served exclusively over HTTPS.
3. Content Requirements
3.1. The app must provide practical functionality that extends Flowlu's capabilities. Apps whose primary purpose is advertising, redirecting to an external resource, or promotion without a useful function are not permitted.
3.2. The description and screenshots must accurately reflect the app's actual functionality. Misleading or exaggerated materials are grounds for rejection.
3.3. The app name and icon must not create the impression of official affiliation with Flowlu where no such affiliation exists.
3.4. All listing text must be in English. Portuguese and Spanish are optional but recommended.
4. Prohibited Content
The following are prohibited in the app and its listing:
-
malicious code or scripts for unauthorized data collection;
-
materials that violate any applicable laws or regulations;
-
adult, discriminatory, or offensive content;
-
infringement of third-party trademarks or copyrights.
5. Publication Process
5.1. The Developer submits the app for review through the Developer Account. Only apps with a fully completed listing are accepted for review. Flowlu aims to complete reviews within a reasonable timeframe.
5.2. Flowlu reviews the app against these requirements and makes one of the following decisions:
-
Publish — the app appears in the Marketplace;
-
Revise — Flowlu specifies what needs to be corrected;
-
Reject — the app does not meet the requirements.
5.3. After publication, Flowlu may remove an app from the Marketplace at any time upon discovery of a violation or at its sole discretion.
5.4. Changes to a published app that affect its functionality or OAuth Permissions require a new review. During the review period, previously installed Users retain access to the previous version of the App.
5.5. Technical details on working with the JS SDK, REST API, sandbox Portal, and the release process are described in the Developer Guide. The Developer Guide is a mandatory document on equal footing with these Requirements.
