{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiadtvxmna6icq6vqnljvaggfuhwnvl7iawmhuhw67jnmo5qan7ski",
    "uri": "at://did:plc:34cg4tn4iwemk3v5k3n3adwf/app.bsky.feed.post/3mk6635lg3fc2"
  },
  "path": "/t/moving-to-distributing-self-signed-apks/34312#post_1",
  "publishedAt": "2026-04-23T10:42:12.000Z",
  "site": "https://forum.f-droid.org",
  "tags": [
    "Orgro | F-Droid - Free and Open Source Android App Repository",
    "Reproducible Builds | F-Droid - Free and Open Source Android App Repository"
  ],
  "textContent": "I currently distribute my app ( Orgro | F-Droid - Free and Open Source Android App Repository ) on Google Play and on F-Droid. With the Google Android developer verification process I have claimed the package name for my private key. I understand that means that in the (near?) future, some users may have difficulty running or installing my app if it is not signed with my key.\n\nCurrently the F-Droid builds are signed by F-Droid. I understand that I can get F-Droid to distribute my own APKs as long as they are reproducible against the F-Droid APKs (“Publishing APKs with the upstream developer’s signature” on Reproducible Builds | F-Droid - Free and Open Source Android App Repository).\n\nI do my development on a Mac. Is there any guidance for how to reproduce the F-Droid build environment such as in a Docker image?",
  "title": "Moving to distributing self-signed APKs"
}