Publish your Android app in the AppForShare store
Every plan with an account (public repositories); private repositories on Pro and Team
Android lets people install apps from outside Google Play, but they have little to go on when they do: an APK on a download site says nothing about where it came from. The AppForShare store answers that for every app it lists. Each APK is built from the source code at a tag you name, by our published build workflow, and each release is reviewed before it goes out.
Your app gets a page at store.appforshare.io with the version, the APK SHA-256, the signing certificate, the permissions in plain words and the source and commit it was built from. 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.
Example
Store, com.example.notes
- SourceGitHub, tag v2.3.0
- ReviewPassed, no trackers
- SigningSigned
- AppForShare storeLive
Made for
- Open source Android developers who want a second home next to F-Droid and Google Play
- Indie developers and small teams who ship an APK outside Google Play
- Teams that want one reviewed release for their own site, the store and Google Play
What it ends
- An APK on your site with no way for users to check where it came from
- Waiting days for a store to build and publish a new version
- Building, signing and uploading the same release by hand for each place it goes
How it works
Step 1
Set up the store app
Open your project's Store page, enter the package name and the GitHub repository, and prove you own the package name with a claim token.
Step 2
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, and the build is attested so we know which commit and workflow made it.
Step 3
Review and signing
Every release is reviewed automatically: permissions, trackers, known malware, code that loads other code, the app's images and name, and an AI review of what the checks find. A passed release is signed with a key made for your app, by you, or with your own keystore on Team.
Step 4
Live in the store
The release goes live at store.appforshare.io and in the F-Droid compatible repository within minutes. You can send the same reviewed release on to Google Play and the App Store from your own accounts.
What people see on your app page
Download APK with the version, size and the SHA-256 of the signed file, the signing certificate, the source repository, tag and commit, the date of the review, the permissions in plain words, the trackers our check found and the anti features you declared. If you sell in the EU, the trader details you gave are shown as the law asks.
The store front lists live apps by category and shows which apps were updated recently. Every page has Report this listing, and rights holders can send a copyright or trademark notice with evidence.
How a release is reviewed
Every release is reviewed automatically by our checks and an AI review, with guardrails in code; staff can look at any decision later. 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.
Live APKs are scanned again every week with the newest malware signatures. A hit withdraws that version at once, and F-Droid clients that read our repository warn the people who installed it. The rules and live numbers are on the store's transparency page.
Updates in the apps people already use
The store is an F-Droid compatible repository (index-v2) with a signed index. People add it once in F-Droid, Droid-ify or Neo Store, or follow one app in Obtainium, and each new release shows up there with the rest of their apps.
Copies installed from Google Play cannot update from the store, because Google Play signs apps with its own key. That is the same for F-Droid and every other store.
Plans
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 and more store apps. Team adds maintainers per app, more store apps, and signing with your own imported keystore. See the pricing page for the number of store apps on each plan.
Good to know
- 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.
- Paid apps and in-app purchases through the store are not offered.
- A review lowers the risk, it does not remove it. We never call an app safe; the pages say built from reviewed source.
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. You can send the same reviewed release to Google Play from AppForShare, using your own Play connection.
- Who signs my app?
- You choose: AppForShare signs with a key made only for your app, you sign our reviewed build yourself with the CLI, or on Team we sign with your own imported keystore. The certificate is shown on your app page.
- Does a person approve each release?
- No. Every release is reviewed automatically by our checks and an AI review, and goes live within minutes when it passes. Staff can look at any decision later.
- Can I list a closed source app?
- Yes, on Pro and Team, from a private GitHub repository through the AppForShare Builds GitHub app. The source is never published; the page says it was built from a private repository.
- How do people get updates?
- From the app page, or in F-Droid, Droid-ify, Neo Store or Obtainium after they add our repository once.
Read next
Try it on your own app
Free account in a minute. Pro starts with a 7 day free trial.
More features
- Builds on GitHub Actions
- Flutter builds on GitHub Actions
- Flutter facts and checks
- Security scan on every build
- Connect Expo (EAS builds)
- Connect Codemagic
- Send store builds to TestFlight and Google Play
- TestFlight groups and beta review on send
- TestFlight feedback in your inbox
- iOS device registration
- Hands free device setup
- Store listing editor
- App Store submission
- Google Play releases
- TestFlight tester sync
- Tester app with notifications
- Tester groups and status
- Join links for testers
- Beta and Live channels
- Build history page
- Tasks and activity feed
- Feedback to Linear and Jira
- Release checklist, approvals and blockers
- Release page per version
- Install link controls
- Several links per build
- Retire a test build
- TestFlight and APK in one link
- Install page in 13 languages
- In-app update check
- .aab uploads
- MCP server for AI tools
- Tester feedback with screenshots
- In-app feedback link
- AI test plan for each build
- Diawi compatible upload API
- Remember my iPhone
- Install help and why it failed
- Email the install link
- Custom channel address
- Verified publisher
- Daily install email
- Zipped .app upload
- Manage link for guest uploads
- Test accounts on the install page
- Telegram notifications
- Permissions in plain words
- Reply to testers and star ratings
- Follow a channel by email
- Download button for a README
- Store pages
- Check a build before upload
- Token scopes and CLI tools
- Upload from Claude or ChatGPT
- Passkeys and email code sign in
- Free build tools
- How reports work
- Malware check on every upload
- Re-sign iOS builds
- Single sign on (SAML and OpenID Connect)
- Require two step sign in
- Send to Microsoft Intune
- Choose where build files are stored
- Mac and Windows builds
- Workspace address
- Automatic clean up of old builds
- Tester email from your own mail server
- Webex notifications