A complete listing
Name, summary, description, categories, version and release notes. Include your homepage, support and privacy-policy links.
FOR DEVELOPERS
Made by you.
Reviewed with care.
Bring your app to the enzim collection.
A public submission, a clear review, and a signed release.
Public-source apps · GitHub account required · No submission fee
BEFORE YOU BEGIN
Give your app a good introduction.
Real screenshots
One to eight current PNG, JPEG or WebP images with captions. Show the actual app, without private data. Minimum 640 × 360; maximum 3840 × 2160.
Reviewable packaging
Public source pinned to a full commit, a JSON Flatpak manifest and AppStream metadata. Explain every sandbox permission.
A recognisable identity
A square PNG icon, a stable app ID, a redistributable licence and the maintainers authorised to publish updates.
Screenshots: up to 8 MiB each. Icon: square, 128–1024 pixels, up to 2 MiB; 512 pixels recommended. Read the full requirements ↗
A SIMPLER WAY TO PUBLISH
Your repository.
Your release.
Sign in with GitHub, connect the public repository you maintain, and choose a release. We fill in the version and release notes and lock its source for review.
Add your listing, icon and screenshots, then submit here. Setup changes are prepared and approved from the dashboard. No manually copied commit is required. If your repository needs Flatpak packaging, request help during submission.
Open developer dashboard ↗- Connect GitHub
Connect only the repositories you choose. Approve automatic build setup here.
- Select a release
We find available packaging and prefill release details.
- Complete your listing
Add screenshots, privacy details and anything reviewers should know.
- Submit for review
Track feedback here. For an update, choose your app and its new release.
Advanced packaging contributors can still use the public review repository ↗.
A CLEAR REVIEW PROCESS
Know where things stand.
Submitted→In review→Approved for build→Testing→Published
A reviewer may request changes or more information. Approval and publication are separate: an app appears in the store only after the reviewed build passes testing and signed promotion. Review status and feedback are shown in your dashboard and the public review queue; no review time is guaranteed.
KEEP YOUR APP CURRENT
Update from your next release.
Open your app in the dashboard, select its new GitHub release, and review the prefilled version and notes. Your listing and screenshots are kept for you to update when needed.
Submit an update ↗Every release is reviewed.
New permissions, source-host changes, privacy changes and maintainer transfers need renewed review. Adding your username to a proposed update does not grant access to an existing app.
Builds receive no release keys or deployment credentials. Metadata checks do not establish app safety, and a merged PR does not automatically publish software.
Ready when you are.
Prepare your first submission, or read the public packaging and review policies.