An F-Droid client with modern UI and an arsenal of extra features.
4.8k
Stars
165
Forks
122
Open issues
30
Contributors
AI Analysis
Neo Store is a modern F-Droid client for Android that replaces the default F-Droid app with improved UI/UX, faster repository syncing, and built-in repository management. It is purpose-built for Android users who want to browse and install free and open-source applications from F-Droid repositories with a contemporary interface; it is not a general-purpose app store and requires familiarity with the F-Droid ecosystem.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Modern F-Droid client with expanded repository support and polished UI, competing in an active niche
Neo Store is a Kotlin-based F-Droid client designed as a modern alternative to the official F-Droid client, emphasizing UX, fast sync times, and built-in support for ~100 repositories. It targets Android users who prefer open-source software and want a more feature-rich app store experience than the official client. Adoption appears concentrated within the privacy-conscious and F-Droid enthusiast communities rather than mainstream Android users.
Neo Store launched in March 2021 as part of the broader NeoApplications ecosystem (which includes Neo-Launcher). It entered a market already served by the official F-Droid client (since 2010) and later competitors like Droid-ify. The project reflects a trend of specialized Android clients prioritizing user empowerment and modern Material Design.
The project accumulated 4,775 stars over ~5 years, gaining 17 stars in the last 7 days (as of 2026-07-08). Last push was 2026-04-26, indicating active maintenance but modest recent velocity. Growth appears steady rather than accelerating, suggesting established niche rather than expanding market share. The presence on multiple distribution channels (F-Droid, IzzyOnDroid, GitHub, Codeberg) indicates stable uptake within open-source communities.
Adoption not verified through quantified metrics. Presence on official F-Droid repository and IzzyOnDroid (both curated stores) implies basic quality standards met. Community channels (Telegram, Matrix) exist but member counts not disclosed. Real-world user base size and retention metrics are opaque. Higher star count than official F-Droid client (4,775 vs 2,883) may reflect user preference or GitHub visibility rather than market dominance.
Written in Kotlin for Android. README emphasizes UX, fast sync, and repository management but provides no technical architecture details. Appears to implement F-Droid client protocol and repository indexing, likely with Material Design UI framework. Reproducible build support is explicitly highlighted.
Not documented in README. No mention of testing strategy, CI/CD practices, or code coverage metrics.
Last push 2026-04-26 (72 days before analysis date) indicates ongoing maintenance. Project has 165 forks and active Weblate translation integration, suggesting community engagement. Codeberg roadmap board mentioned suggests planned future work. Activity pattern is consistent with steady maintenance rather than rapid development or abandonment.
ADOPT IF: you actively use F-Droid and value UI polish, repository exploration, or support for multiple sources beyond the official repository; or you are developing alternative F-Droid clients and want to reference a well-maintained Kotlin implementation. AVOID IF: you need enterprise support, guaranteed backwards compatibility across major OS versions, or a category leader with documented large-scale adoption; or if your primary use case is Google Play Store access. MONITOR IF: you are building privacy-focused app ecosystems and want to track how alternative F-Droid clients evolve; or you depend on F-Droid infrastructure and need to understand client-side fragmentation.
Independent dimensions
Mainstream potential
3/10
Technical importance
5/10
Adoption evidence
3/10
- Adoption metrics are opaque — real user base size, retention, and crash rates are not publicly disclosed, making it difficult to assess production maturity.
- Dependency on F-Droid repository protocol and third-party repository stability; if major repositories fail or change format, client must adapt quickly.
- Fragmentation risk: multiple F-Droid clients (Neo Store, Droid-ify, official) may dilute user base and community contribution volume, reducing long-term resilience.
- Maintenance concentration: likely depends on small core team; extended absence or burnout could stall development despite current activity.
- No documented security audit or formal threat model; privacy claims are not independently verified.
Neo Store will likely remain a stable, niche alternative within open-source Android communities for the next 2–3 years. Adoption probably will not expand beyond F-Droid enthusiasts without significant marketing or platform integration. Maintenance appears sustainable at current velocity but unlikely to accelerate unless major catalyst (e.g., official F-Droid client abandonment) occurs.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- Kotlin
- License
- GPL-3.0
- Last updated
- 3mo ago
- Created
- 65mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
[Bug] Crash when opening Clench Wallet
[Bug] Sync dir making error ENOENT
[Feature Request] Default tab option
[BUG] old changelog is shown although newer update from other source is available
[Feature Request] Download APKs in Custom download folder with name+version
Top contributors
Similar repos
f-droid/fdroidclient
F-Droid Client is the official Android application for F-Droid, a free software...
NeoApplications/Neo-Launcher
Neo Launcher is a feature-rich, AOSP-based Android launcher that provides...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
NeoApplications/Neo-Store
this
|
4.8k | +13 | Kotlin | 7/10 | 3mo ago |
|
f-droid/fdroidclient
|
2.9k | — | Kotlin | 8/10 | 1d ago |
 Droid-ify/client
|
7k | — | Kotlin | 8/10 | 2w ago |
|
NeoApplications/Neo-Launcher
|
2.1k | — | Java | 7/10 | 4d ago |
 whyorean/AuroraStore
|
2.7k | — | Kotlin | 7/10 | 3d ago |
 MobileNativeFoundation/Store
|
3.4k | — | Kotlin | 8/10 | 4w ago |
Official reference implementation (2,883 stars). Neo Store likely offers more polished UI and additional repository support; official client has authority and guaranteed compatibility but slower UI iteration.
Higher star count (7,005). Both are modern alternatives to official client; unclear which has larger actual user base. Droid-ify may have superior market penetration or GitHub visibility.
Focused on Google Play Store mirroring (2,641 stars). Serves different use case (proprietary app access) whereas Neo Store emphasizes F-Droid ecosystem. Not direct competitors.
Data persistence library (3,405 stars). Entirely different category; no competition.
Sibling project (2,063 stars) in same organization. Neo Store has higher adoption, suggesting stronger market fit or user interest in app distribution vs. launcher customization.
