Developer Documentation
  • Developer Docs
  • Writing Apps
    • The Basic Setup
    • Hello World
    • Our First App
      • Metadata
      • The Build System
      • Translations
      • Icons
      • Packaging
      • Continuous Integration
    • Boxes and Grids
    • Popovers
    • Panes
    • Code Style
      • GObject-style Construction
    • Creating Logs
  • APIs
    • Actions
    • Notifications
    • Launchers
    • State Saving
    • Custom Resources
    • Color Scheme
    • System Settings
    • Valadoc
  • AppCenter
    • Publishing Requirements
    • Submission Process
    • Monetizing Your App
    • Publishing Updates
    • Markdown Badges
    • Dashboard
Powered by GitBook

Links

  • Homepage
  • Support
  • Developer
  • Blog

Other Docs

  • HIG
  • Contributor Guide

Made with ❤️ by contributors from all over the world

On this page
  • Create a New Release
  • Submit for Review
  • Wait for Testing
  • Resolve Issues
  • Available on AppCenter
  • Publishing Updates

Was this helpful?

Edit on GitHub
Export as PDF
  1. AppCenter

Submission Process

The submission process for AppCenter, broken down into a few short steps

PreviousPublishing RequirementsNextMonetizing Your App

Last updated 2 years ago

Was this helpful?

Please make sure to review before submitting your app

Create a New Release

Before you can publish your app, you'll need to . It is important that you use a without a pre-release tag when releasing.

Submit for Review

It is important to before completing this step

To submit your app to AppCenter, you'll need to create a new JSON file describing your app release in the AppCenter Reviews repository on Github:

Name the file using your app's id with the json file extension. Fill in the contents of the file with the link to your git repository, the commit hash from your latest release, and the version number of that release:

io.github.myteam.myapp.json
{
  "source": "https://github.com/danirabbit/harvey.git",
  "commit": "45dd52660c0069207fa4b0c1fcf7ac6d7157d34b",
  "version": "1.0.1"
}

Once you've submitted the new file as a pull request to the AppCenter Reviews repository, your app will now be in the review queue!

Wait for Testing

Resolve Issues

Your app will go through an automated build process when it has been accepted by a reviewer. It will need to pass the Parse and Build steps listed in GitHub CI at the bottom of the pull request. If either of those steps fail, please inspect the build log to resolve issues.

If any questions or requested changes come up during the review process, the reviewer will use the conversation on the pull request and may mark it as "Changes Requested". You will need to correct these issues, create a new release of your app, and update the pull request with your new release.

The reviewer may also make some suggestions for best practices, inform you of new features, or link you to documentation.

Available on AppCenter

When your app passes automated testing and human review, it will become available in AppCenter in elementary OS.

Publishing Updates

The source field needs to be a publicly accessible Git repository. The commit field is the full Git sha for the release you're submitting. And the version field needs to be a tag.

All apps and updates in the review queue are listed as . Once a pull request is approved and merged by a reviewer, that app will be published to the . Depending on demand, this may take several days.

If you wish to , you can restart the submission process by creating a new release on GitHub. Then navigate to the , modify your app's json file with the latest commit hash and release tag, and submit that change as a pull request to begin a new review process.

SemVer
open pull requests
AppCenter Flatpak repository
publish an update
AppCenter Reviews Github repository
the publishing requirements
release it on GitHub
Semantic Versioning Number
make changes to your app's monetization status
https://github.com/elementary/appcenter-reviews/new/main/applicationsgithub.com
Select this link to automatically open a new file in the correct location