RepoStore discovers apps automatically through the public GitHub Search API. There is no private index and no manual curation. If your repository is public, ships an APK in its latest release, and is discoverable by search, RepoStore can find it and show it like a Play Store listing — with your README as the description and your screenshots in a gallery.
Check if your repo is compatiblepublic)..apk asset (auto-generated source zips are ignored).README.md at the repo root (rendered as “About this app”).screenshots/ folder with image files (shown in the gallery).android, mobile, apk for discovery.Push your Android project to a public GitHub repository. Add a clear description and topics (android, apk, plus your app category) so search can find it.
Go to Releases → Draft a new release, create a tag (e.g. v1.0.0), write release notes, and upload your signed .apk as an asset. Publish it (not as a draft or prerelease).
RepoStore always installs from your latest published release, so keep new versions coming as new releases.
Place a README.md at the repo root. RepoStore renders it as the “About this app” section, so describe what the app does and list its features. See the template below.
screenshots/ folderAdd a folder named screenshots/ at the repo root and drop your app screenshots in it (.png or .jpg). These appear in the details screen gallery with a fullscreen viewer.
Use portrait screenshots at a consistent size for the cleanest gallery.
That’s it — there’s no submission form. Once your repo meets the requirements, RepoStore can surface it through search. Stars and good topics improve how likely it is to appear in the Trending, Recently Updated, and Featured sections.
Here is a minimal layout that works well with RepoStore:
your-app/
├── app/ # your Android app module
├── screenshots/ # images shown in the RepoStore gallery
│ ├── 1.png
│ ├── 2.png
│ └── 3.png
├── README.md # rendered as "About this app"
├── build.gradle.kts
└── settings.gradle.kts
Release (on GitHub → Releases):
└── v1.0.0
└── app-release.apk # the installable APK asset
Copy this into your repo’s README.md and adjust the details:
# TODO App
A simple, clean to-do list app for Android built with Kotlin
and Material 3.
## Features
- Add, edit, and delete tasks
- Mark tasks as complete
- Offline-first with local storage
- Light and dark themes
## Screenshots
Screenshots are in the [screenshots/](screenshots/) folder.
## Download
Grab the latest APK from the
[Releases](../../releases/latest) page,
or install it through RepoStore.
## License
MIT
samyak2403/TODOApp is a working example of a RepoStore-ready repository. It has everything RepoStore looks for:
app/ Android module.README.md describing the app.screenshots/ folder with preview images..apk.Use it as a reference when structuring your own project.
View TODOApp on GitHubNo. RepoStore finds apps automatically through GitHub search. Just meet the requirements and keep your repo public.
The most common reasons: the latest release has no .apk asset, the release is a draft/prerelease, the repo is private/archived, or it isn’t discoverable via search yet. Add relevant topics and a few stars help.
Always the latest published release. Ship each new version as a new GitHub Release with the updated APK.
Standard web image formats such as .png and .jpg placed inside the screenshots/ folder.