# Neo Store: an F-Droid client for Android users who want a modern interface > Neo Store is a GPL-3.0 Kotlin Android client for F-Droid repositories, published on F-Droid, IzzyOnDroid, Codeberg and GitHub. It ships around 100 built-in repos and reproducible build labels, but it is still an F-Droid client underneath, so its catalogue is only as good as the repositories you enable. **NeoApplications/Neo-Store** — An F-Droid client with modern UI and an arsenal of extra features. - Repository: https://github.com/NeoApplications/Neo-Store - Stars: 5,296 · Forks: 187 - Language: Kotlin - License: GPL-3.0 - Published: 2026-09-23 · Updated: 2026-09-23 · Language: en - Canonical page: https://hysenlabs.com/projects/neoapplications-neo-store ## What Neo Store solves for F-Droid users F-Droid is a repository of free and open source Android applications, and the official client is functional but sparse. Neo Store is a client for that same repository model, built around a different interface: the README describes it as "the modern and feature-rich F-Droid client for everyone" and lists an UX focus, fast repository sync times, built-in repositories, and app exploration among its features. The intended audience is an Android user who has decided to get apps from F-Droid-compatible repositories rather than the Play Store, and who cares about how the client looks and how quickly it refreshes. The project itself is a direct adaptation of Foxy-Droid, per the README, and is licensed GPL-3.0 or later. It is not a new app distribution network. Everything it installs comes from repositories that the F-Droid ecosystem already knows about, which means the client's value is in the browsing, filtering and repository management layer, not in the catalogue. ## How the repository model works in Neo Store The mechanism is the F-Droid repository format. A repository is an index of APKs with metadata, and a client fetches that index, displays the apps, and downloads and installs the APK the user selects. Neo Store's README states it ships around 100 built-in repos and gives comprehensive control over your repos, which means the client comes preloaded with a list of index URLs rather than asking you to add each one by hand. That preloading is the main architectural difference from the stock F-Droid client, which starts with a smaller default set. It is also the main thing to think about: every enabled repository is a source you are trusting, and the README does not describe a review process for the built-in list. The screenshots in the repository show a repos screen and a repo detail screen, and a privacy panel, which suggests per-repository information is surfaced in the UI. Reproducible build labels are also shown, matching the badge the README carries for com.machiav3lli.fdroid. A reproducible build label is a signal that a binary was rebuilt from source and matched; it is not a guarantee about every app in every repository. ## Installing Neo Store and syncing your first repository The README points to four distribution channels: F-Droid, IzzyOnDroid, Codeberg releases and GitHub releases. There is no build-from-source install documented in the README for end users, so the practical route is to install from one of those channels. If you want to build the project yourself, the repository is a Gradle Kotlin project with a gradlew wrapper at the top level, and the README does not provide build instructions. On the F-Droid channel, the package identifier is com.machiav3lli.fdroid, and the F-Droid page for that package is the install entry point: ```bash # open the F-Droid listing in a browser https://f-droid.org/packages/com.machiav3lli.fdroid ``` After installing, the first real use is a repository sync. Open the app and let it refresh its index; the README claims fast repository sync times as a feature, and the repos screen shown in the repository's screenshots is where the built-in list is managed. From there, browsing and filtering is the normal path to finding an app. The README does not document a command-line interface, an API, or a self-hosted server component, so there is nothing to configure outside the app. ## Where Neo Store is the wrong tool Neo Store cannot install apps that are not published in an F-Droid-compatible repository. If the app you want exists only on the Play Store, this client will not find it, and no amount of repository configuration changes that. The README makes no claim otherwise. The second limitation is trust surface. Around 100 built-in repositories means around 100 index URLs the app can draw from, and the README does not document how that list is curated or whether repositories can be marked as untrusted. A user who wants a minimal, auditable set of sources is better served by adding repositories manually in a client that starts empty. Third, the README does not document rollback of an app version or a downgrade path, so if a new release of an installed app breaks something, the documented material gives no recovery procedure. That is a real gap for anyone managing apps on a device they depend on. ## Neo Store compared with the stock F-Droid client and Droid-ify The difference between Neo Store and the official F-Droid client is mostly presentation and default configuration. Both speak the same repository protocol and install the same APKs. Neo Store arrives with a larger built-in repository list and a UI the project describes as modern, plus filters and a privacy panel visible in its screenshots. The official client is the reference implementation and is maintained by the F-Droid project itself; Neo Store is a third-party adaptation of Foxy-Droid. Droid-ify is the other comparison people search for, and it is another third-party F-Droid client with its own interface choices. The honest difference is that these clients are alternative front ends over one protocol, so the decision comes down to interface, default repositories and which one you find easier to operate. None of them expands the catalogue beyond what the repositories contain. If you are comparing Neo Store against Aurora Store instead, that is a different question entirely: Aurora Store fronts the Play Store, which is a different catalogue with different licensing. ## Maintenance, releases and what the GPL-3.0 licence means here The repository is not archived, and the last push was on 2026-09-20. The most recent release listed is 1.3.0, published the same day, following 1.2.6 in April 2026 and 1.2.5 in March 2026. The cadence in that record is uneven: two releases in spring, then a gap until September. The README also notes that a maintainer, Iamlooker, stepped away and forked the project for career reasons, which is worth knowing when you judge how many people are carrying the work. Upgrade cost is low in the ordinary case, because Android app updates arrive through the store itself or through the channel you installed from. The licence is GPL-3.0 or later, and the README states the project is a direct adaptation of Foxy-Droid. If you plan to redistribute a modified build, the copyleft terms of the GPL apply to your distribution; that is a statement about the licence text, not legal advice, and you should read COPYING in the repository and take your own advice if you are shipping something commercial. ## Conclusion Install Neo Store if you already trust F-Droid's model but find the default client's interface dated, and you want a wider set of repositories available out of the box. Skip it if you need Play Store apps or a store that works without repository sync. Before adopting it, verify one thing: that the repositories you actually need are present in its list, and that the app you want is published there. ## FAQ ### What is Neo Store? It is an F-Droid client for Android with a modern UI, written in Kotlin and licensed GPL-3.0 or later. The README describes it as a direct adaptation of Foxy-Droid and lists around 100 built-in repositories. ### Is Neo Store free to use? The project is licensed under GPL-3.0 or later, and the README points to F-Droid, IzzyOnDroid, Codeberg and GitHub as distribution channels. The README does not describe a paid tier. ### How do I install Neo Store? The README links four channels: F-Droid, IzzyOnDroid, Codeberg releases and GitHub releases. The F-Droid package identifier is com.machiav3lli.fdroid. The README does not document building from source for end users. ### Is Neo Store safe? The README does not make a security claim. What it does state is that reproducible build labels are shown in the app, matching the badge it carries for com.machiav3lli.fdroid. Every app still comes from whichever repositories you have enabled. ### How does Neo Store compare with F-Droid? Both use the same repository protocol and install the same APKs. Neo Store differs in interface and in shipping around 100 built-in repositories, and the README notes it is a direct adaptation of Foxy-Droid. The official client is maintained by the F-Droid project. ### What alternatives to Neo Store exist? Droid-ify is another third-party F-Droid client with its own interface, and the official F-Droid client is the reference implementation. Aurora Store is a different kind of tool because it fronts the Play Store catalogue rather than F-Droid repositories. ## Sources - [Issues](https://github.com/NeoApplications/Neo-Store/issues) - [License: GPL-3.0](https://github.com/NeoApplications/Neo-Store/blob/master/LICENSE) - [NeoApplications/Neo-Store on GitHub](https://github.com/NeoApplications/Neo-Store) - [README](https://github.com/NeoApplications/Neo-Store/blob/master/README.md) - [Releases](https://github.com/NeoApplications/Neo-Store/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/neoapplications-neo-store