Summary: A self-hosted F-Droid repository at fdroid.randogoth.com, fed straight from Forgejo releases, now serving Muzzle Velocity, Plasmoid, The Mews and kirakira.
Until this week, installing one of my Android apps meant finding the APK on a release page and tapping through the warning about unknown sources. I don't think anyone did that twice. Now there is an *F-Droid* repository at `fdroid.randogoth.com` with four apps in it: [Muzzle Velocity]({filename}20260619_muzzle.md), [Plasmoid]({filename}20260619_plasmoid.md), *The Mews* from the [Mews Profile]({filename}20261013_mews-profile.md) post and *kirakira* from the [smolmail clients]({filename}20261013_smolmail-clients.md) post.
Nothing gets built on the server. Each app's own *Forgejo* workflow signs its APK when I push a tag, a webhook tells the repo, and the listing (title, description, changelog, screenshots) is read from the app's `fastlane/` folder at that same tag, so it can't describe a build other than the one it ships. The one surprise was that the release webhook fires one API call *before* the APK gets attached, so the server kept turning up to an empty release... It waits for the upload now. *kirakira* supplied the humbling number: thirteen commits, eleven of them fixes to its release workflow.
