Submit an App

Anyone can suggest an open-source app for OpenLib. Submissions are reviewed before they appear in the public library.

How app submission works #

Submitting an app is a structured review request. The submitter provides metadata, links, categories, tags, platform support, and context about what the app replaces. Maintainers review that information before the app becomes public.

The workflow is intentionally conservative:

1. A user submits a candidate app.
2. OpenLib stores the submission for review.
3. Maintainers check source availability, license, safety, and metadata quality.
4. The submission is approved, rejected, or sent back for changes.
5. Approved apps become public library entries.

This keeps the public library useful without making every visitor judge raw, unreviewed submissions.

Before you submit #

Make sure the app has:

• A public source repository.
• A clear open-source license.
• A stable project name and homepage or release page.
• Enough description for a new user to understand what it does.
• Accurate platform and category information.

How to use the submit form #

Use the form as if you were explaining the project to someone who has never heard of it.

1. Enter the official project name.
2. Write a short description in plain language.
3. Add the source repository URL.
4. Add the official website or release page when available.
5. Choose the closest category.
6. Add tags that describe features, platforms, protocols, and workflows.
7. List proprietary apps or services this project can replace.
8. Add platform and install information.
9. Review all links before submitting.

If you maintain the project, include enough context for reviewers to confirm ownership and official links.

Submission fields #

Review flow #

1. Submit the app from the OpenLib website.
2. A maintainer checks source, license, category, and safety signals.
3. The submission is approved, rejected, or sent back for changes.
4. Approved apps become public and can receive reviews and edit requests.

Markdown example for maintainers #

## Review notes

- Source repository is public.
- License is listed in the repository.
- Category and platforms match project documentation.

Common rejection reasons #

• No source code is available.
• License is missing or not open source.
• Download link points to unsafe or unrelated files.
• The app is abandoned and has known severe security issues.
• The submission duplicates an existing OpenLib entry.

Submission quality checklist #

Before pressing submit, confirm:

• The source URL opens without authentication.
• The license is visible in the repository or website.
• The project name matches the upstream project.
• The description does not make unsupported claims.
• Download and website links point to official project resources.
• Tags are useful for discovery and not promotional.
• The app is not already listed in OpenLib.