How to publish an Android app without Google Play, for free
· 8 min read
You can publish an Android app without Google Play in three common ways: put the APK on your own website, get it into F-Droid, or list it in the AppForShare store, a public Android store that opened in November 2026 at store.appforshare.io. Listing an app built from a public GitHub repository is included on every AppForShare plan with an account, the Free plan too. This post explains how the store works, what your users see, and where it fits next to the other options.
The short version: every app in the store is built from source by our published workflow in your own GitHub Actions, reviewed automatically, signed, and published on a page that shows the APK SHA-256 and the signing certificate. The store is also an F-Droid compatible repository, so people who use F-Droid, Droid-ify, Neo Store or Obtainium get your updates there.
Why publish outside Google Play at all
Android lets people install apps from outside Google Play, and plenty of developers have good reasons to ship that way. Open source projects want their users to get builds that match the code. Indie developers want a second channel that does not depend on one account. Some apps serve people who avoid Google services altogether.
The problem is trust. An APK on a download page says nothing about where it came from. The user cannot tell which commit it was built from, who signed it, or whether anyone looked at it. The AppForShare store was built to answer those questions on every app page.
Ways to publish an Android app without Google Play
| Option | Who builds the APK | How users get updates | Fits best |
|---|---|---|---|
| APK on your own website | You, on your own machine or CI | They come back and download again, or you build your own update check | Apps with an existing audience that trusts your site |
| F-Droid main repository | F-Droid's build servers, from your source | F-Droid and compatible clients | Fully free and open source apps that meet F-Droid's inclusion rules |
| GitHub releases with Obtainium | You | Obtainium watches your releases | Technical users who follow one project |
| AppForShare store | Our published workflow in your own GitHub Actions, from a tag or commit | The store, plus F-Droid, Droid-ify, Neo Store and Obtainium | Open source and closed source apps that want a reviewed, signed release with a public page |
These are not either or. Many projects stay in F-Droid and also list in the AppForShare store, and many keep Google Play as well. You can send the same reviewed release on to Google Play from your own Play connection with Google Play releases.
How a release goes from your repository to the store
- Set up the store app. Open your project's Store page in AppForShare, enter the package name and the GitHub repository, and prove you own the package name with a claim token.
- Add the build workflow. Add our published workflow to your repository. Each tag you push builds the release APK on a fresh GitHub hosted machine in your own GitHub Actions. The build is attested, so the store knows which commit and which workflow made it.
- Automatic review. Every release is checked for permissions, trackers, known malware and code that loads other code, and an AI review reads what the checks find. A first release, or one that changes the icon, name or package name, also gets an originality check against well known brands, other stores and our own store.
- Signing. A release that passes is signed. You choose how: with a key made only for your app, by you with the AppForShare CLI, or on Team with your own imported keystore.
- Live. The release goes live at store.appforshare.io and in the F-Droid compatible repository within minutes of passing.
No person has to approve each release. The review runs in code with guardrails, and staff can look at any decision later. If a release does not pass, you see why on the Store page and can push a fixed tag.
What people see on your app page
Each app gets its own page at store.appforshare.io with the information a careful user looks for before installing an APK:
- Download APK with the version, the size and the SHA-256 of the signed file, so anyone can compare the file they got with the one we published.
- The signing certificate. Android only installs an update signed with the same key as the installed copy, so this is what ties every future update to the first install. Our guide to Android app signing explains why that matters.
- The source repository, the tag and the commit the APK was built from, or a note that it was built from a private repository.
- The permissions in plain words, the trackers our check found and the anti features you declared. For more on reading permissions, see Android permissions in plain English.
- The date of the review, and a Report this listing link on every page.
The store front lists live apps by category and shows which apps were updated recently. The rules the review follows, and live numbers about it, are on the store's transparency page.
Weekly rescans after release
A review on the day of release is not the end. Live APKs are checked again every week against the newest known malware signatures. A match withdraws that version at once, and F-Droid clients that read our repository warn the people who installed it. A review lowers the risk of a bad app reaching people; it does not remove it, which is why the store pages say built from reviewed source and make no stronger promise.
Updates in F-Droid, Droid-ify, Neo Store and Obtainium
The AppForShare store is an F-Droid compatible repository with a signed index in the current index-v2 format. A user adds it once in F-Droid, Droid-ify or Neo Store with the address and fingerprint on the repository page, or follows a single app in Obtainium through its F-Droid third party repository source. From then on, each new release of your app shows up in the app they already use for updates, next to the rest of their apps.
The fingerprint is the SHA-256 of the certificate that signs the repository index. The client checks every index against it, so a copy of the repository signed by someone else is refused.
One limit applies to every store, F-Droid included: a copy installed from Google Play cannot update from another store, because Google Play signs apps with its own key. A user who wants updates from the AppForShare store installs the store copy instead of the Play copy.
Public and private repositories
Every plan with an account can list apps built from a public GitHub repository, with the automatic review, signing and unlimited updates. Pro adds apps built from a private GitHub repository through the AppForShare Builds GitHub app; the source is never published, and the app page says it was built from a private repository. Team adds maintainers per app and signing with your own imported keystore. The number of store apps on each plan is on the pricing page.
That makes the store an option for closed source apps too, not only for open source projects. You still get the reviewed build, the public SHA-256 and certificate, and updates through F-Droid clients.
What the store does not do
- There are no paid apps and no in-app purchases through the store. Every app is a free download.
- Builds run through our published workflow in your GitHub Actions. GitLab and plain git sources can be set up now; their builds come with our own builder later.
- The store does not replace Google Play for people who only install from Play. It gives everyone else a reviewed place to get your app, and you keep your Play listing and your Play account.
A note on Google's developer verification
Google has started linking Android apps to verified developers on certified devices, with a wider rollout planned for 2027 that covers apps from any source. It does not stop you from publishing outside Google Play, but it is worth planning for. Our guide to Android developer verification covers the dates, who it affects and what to register. The signing certificate on your store page is the one Android checks updates against, so keep it in your records.
Common questions
Do I keep my package name and my Google Play listing?
Yes. You prove you own the package name once, and your Google Play account stays yours.
Can I list an app that is already in F-Droid?
Yes. Your F-Droid listing stays as it is. Note that F-Droid usually signs with its own key, so a user moving between the two copies has to reinstall, the same as moving from Google Play.
How fast does a new version go live?
Within minutes of passing the automatic review, on the store and in the F-Droid compatible repository.
Does it cost anything to list an app?
Listing an app built from a public repository is part of every plan with an account, the Free plan included. Private repositories need Pro or Team.
Get started
Read how listing works on the AppForShare store feature page, look around the store at store.appforshare.io, then open your project's Store page to set up your first app.


