# Prepare before publishing your app

The Store is where customers discover, install, and manage all Oten and third‑party apps. Any developer can build an app and submit it for review. This page explains the end‑to‑end submission flow, what reviewers look for, and how to avoid common pitfalls.

{% hint style="info" %}
All apps go through four phases: Prepare → Submit → Review → After approval. Expect an initial response within a few business days. Duration depends on the app’s scope, complexity, and how quickly feedback is addressed.
{% endhint %}

## Submission phases at a glance

1. Prepare for submission: verify requirements, quality, security, and assets
2. Submit your app: complete the form in the Developer portal and send for review
3. Review process: address feedback (if any) until approval
4. After approval: monitor analytics, manage reviews, and ship updates via versions

## What to prepare before you submit

Before you click Submit, make sure the essentials below are complete. This avoids back‑and‑forth during review.

Minimum setup:

* Application Info: name, short/long descriptions, category/tags, logo, screenshots, website, support email/URL
* Policies: Website, public privacy policy URL and terms of service URL
* API access (if your app exposes APIs to others): define your resource server with permissions, features, and scopes. See [how to declare resource server](/openplatform/about-us/user-guide/oten-developer/3.-declare-application-info.md)
* Review materials: demo credentials or seed data (if needed) and brief reviewer instructions

Pre‑submit checklist (quick view):

<table><thead><tr><th width="140.48828125">Area</th><th width="341.54296875">Must have</th><th>Where</th></tr></thead><tbody><tr><td>App listing</td><td>Name, logo, short/long descriptions, category/tags, website, support</td><td>Application Info</td></tr><tr><td>Policies</td><td>Privacy Policy URL, Terms of service URL</td><td>Application Info</td></tr><tr><td>Auth</td><td>OAuth client with valid redirect URIs; flows tested (PKCE where applicable)</td><td>Configure resources &#x26; security → OAuth</td></tr><tr><td><p>Scopes/</p><p>Permissions</p></td><td>Least‑privilege scopes; if exposing APIs, permissions/features/scopes defined</td><td>Configure resources &#x26; security → resource server</td></tr><tr><td>Pricing</td><td>At least one plan or Free listing</td><td>Pricing &#x26; plans</td></tr><tr><td>Docs</td><td>Quick start, configuration, troubleshooting</td><td>Project docs/README</td></tr><tr><td>Review materials</td><td>Demo account/seed data and short test steps</td><td>Submission form</td></tr></tbody></table>

{% hint style="warning" %}
Apps that do not provide clear, unique value or that heavily duplicate existing marketplace functionality may be declined.
{% endhint %}

## Submit and publish

Submit from the Developer portal once preparation is complete:

<figure><img src="https://gitlab.silvertiger.tech/documents/open-platform/-/blob/document/.gitbook/assets/image%20(14).png" alt=""><figcaption></figcaption></figure>

1. Open Developer portal → App management → App listing.
2. In application Info, confirm listing details and policies are complete (name, icon, descriptions, screenshots, category/tags, website, support, Privacy Policy URL, Terms of Service URL).
3. Open resources & security and verify:
   * If your app exposes APIs for others: resource server has permissions, features, and scopes defined.
   * If your app uses roles: roles link the right features.
4. Click Submit/Publish app to open the submission screen.
5. Provide review inputted information and consent the terms and conditions.
6. Submit.

You will see an on‑screen confirmation; the app status changes Pending approval.

## Review process

What reviewers evaluate:

* Product: core value, UX, stability, accessibility basics
* Engineering: correctness of OAuth, scopes, APIs, and webhooks
* Security: transport/security controls, dependency risk, secrets handling
* Privacy: data minimization, policy clarity, user controls and data rights
* Content and assets: accurate listing, compliant branding
* Support and docs: supportability, troubleshooting, and completeness
* Legal: terms acceptance, licensing/trademarks

If issues are found, you’ll receive feedback via email or a review board. Address the items and resubmit; the team will re‑evaluate. Initial responses typically arrive within 2–3 business days; total time depends on app complexity and iteration speed.

## Phase 4 — After approval

Once approved, your app published onto Oten Store. Keep track on our Developer portal to:

* Monitor analytics and adoption trends
* Manage user reviews and respond to feedback
* Track overall states&#x20;

Ongoing maintenance is required to remain compliant and ensure a great user experience.

## FAQ

**How long does the review take?**&#x20;

Most apps receive an initial response within a few business days. Complex apps or apps requesting sensitive scopes can take longer.

**Why was my app rejected?**&#x20;

Common reasons include missing essential information, over‑broad scopes, unstable auth/config flows, unclear privacy policy, or duplicating existing marketplace functionality without added value.

**Do I need a privacy policy and terms?**&#x20;

Yes. End users are required to consent on these to complete Subscribe app request. Public URLs are required if your app collects or processes user data.

**Can I submit a private or beta app?**&#x20;

This features will be supported.

**What happens if I change scopes after approval?**&#x20;

Requesting new or more sensitive scopes typically requires a new version and trigger re‑review.

**How should I handle user data deletion requests?**&#x20;

Document your deletion/export processes and provide a support contact. Implement automated deletion where feasible.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://oten.gitbook.io/openplatform/about-us/user-guide/oten-developer/6.-publish-your-app/publish-your-app.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.