Publishing

The store is the moderated repository the app ships with. Tweaks are reviewed before they appear, which is the difference between it and hosting your own.

Before you submit

• A .deb that installs cleanly. See Packaging.
• A filter that names its targets. A tweak matching nothing is rejected, and one that loads into everything gets asked why.
• A version in the control file matching the one you are publishing.
• Artwork: an icon, and optionally a hero image and screenshots.
• A GitHub account, which is how the store knows who you are.

Submitting

1. Sign in from the Account tab.
2. Open the Developer Center and choose to publish a tweak.
3. Supply the .deb, the descriptions and the artwork.
4. Submit. It goes into a queue for review.

Artwork is copied into the store rather than linked, so a listing does not break when the place you hosted an image goes away.

What review involves

A moderator checks that the package installs, that the filter is sane, that the description matches what it does, and that nothing in it is hostile. It is not a code audit and does not pretend to be.

Particular attention goes to anything that loads into root processes, since a tweak in a root process runs as root. The app reports that to users before they install, so it is better to target narrowly than to explain later.

Updating

Submit again with a higher version. You can update everything or just one part: the .deb on its own, the screenshots on its own, the video, or the whole listing including the name, descriptions, artwork and category.

Updating only the payload leaves the listing exactly as published, which is what you want for a bug-fix release. Changing the description or artwork does not require a new version of the tweak.

Charging for it

Publishing is the same either way. What changes for a paid tweak is that the download is served privately, and you can have the tweak check its licence before it runs. See Paid Tweaks.