App Fair
The App Fair / Developers

Build and publish with the App Fair

Maintain the app in your own repository. The App Fair reviews each submitted release, builds it, and publishes it through its store accounts.

Getting started →Create your app with personalized commands, then submit its first release.Releases & updates →Versioning, release assets, catalog pull requests and store approval.Troubleshooting →Find the failing stage and the files or settings to fix.FAQ →Developer accounts, app tokens, tools, releases and updates.
From a project to the app storesChoose a token, create and test the app, host the source, publish the website, tag a release, and submit a pull request. The App Fair reviews, signs and submits to Apple and Google. Each step links to its instructions.YOUR REPOSITORY01Choose a tokenA unique project address02Create & testDay + the App Fair template03Host the sourceOrganization / repository04Publish the websitePages + CI walkthroughs05Tag a releasePackages + screenshots06Submit for reviewOne catalog pull requestTHE APP FAIRReview → sign → submit → App Store & Google PlaySubmission steps. Each card links to its instructions.YOUR REPOSITORY01Choose a tokenA unique project address02Create & testDay + the App Fair template03Host the sourceOrganization / repository04Publish the websitePages + CI walkthroughs05Tag a releasePackages + screenshots06Submit for reviewOne catalog pull requestTHE APP FAIR: REVIEW & PUBLICATIONApp Store & Google Play

Before you start

Read the app rules and developer inclusion criteria. The required setup includes the App Fair Publisher installation and a published project website.

You need a GitHub account, permission to create an organization, and a development computer with Rust and Git. Use Day to build the app. You can start with a local web or desktop build; test the mobile targets before submission. Local iOS builds require macOS and Xcode; GitHub CI can build and test iOS when your development computer cannot.

For a first app, open a discussion with its purpose, maintainer and source repository, if one exists. Read the inclusion criteria. Updates to an accepted app go directly to a catalog pull request.

What you maintain

In your app repositoryIn the App Fair catalog
Source, dependencies and license noticesapps/<token>.yaml
UI tests and screenshotsA release tag and its full commit hash
App identity, version and build numberRequested distribution channels
Store text, icon and release notesReview and publication status

Your app lives at github.com/<token>/<token>. The token is an arbitrary, unique project address; it need not match the display name. For example, an app called Field Notes could use Orbit-Notes as its token. Choosing and changing a token explains the constraints.

What the App Fair handles

The catalog runs an independent build and package checks. An App Fair maintainer approves publication, and separate jobs sign and submit the packages using the App Fair’s developer accounts. You do not need to put the App Fair’s signing keys in your repository.

The catalog contribution reference defines the submission fields and current checks. The template contains the starter project and workflow.