Neo-Launcher
2.1k
Stars
151
Forks
148
Open issues
30
Contributors
AI Analysis
Neo Launcher is a feature-rich, AOSP-based Android launcher that provides customization options including themes, gestures, custom widgets, icon packs, and app organization tools. It serves end users who want a modern alternative to stock Android launchers with extensive personalization capabilities. Best suited for Android enthusiasts seeking deep customization rather than casual users wanting a simple launcher experience.
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.
AOSP-based Android launcher with rich theming and gesture support, actively maintained but facing technical barriers
Neo Launcher is a free, open-source Android home screen replacement built on Android Open Source Project foundations. It targets users seeking extensive customization (themes, gestures, icon packs, app organization) without vendor lock-in. Real adoption appears concentrated in the enthusiast/customization community; mainstream adoption metrics are limited. Maintained by a small core team that faced personal and technical obstacles but remains committed to updating for newer Android versions.
Created June 2020 by the NeoApplications collective, Neo Launcher evolved as a spiritual successor to earlier AOSP launcher experiments. It shares DNA with other community-driven launchers like Lawnchair and KISS but positioned itself around modular theming, gesture support, and dashboard features. The project acquired ~2,000 GitHub stars over six years—steady rather than explosive growth.
Stars accumulated gradually and plateaued around 2,000–2,100 range. Recent activity (7 stars in last 7 days, as of 2026-07-09) suggests modest but consistent interest. README explicitly addresses perceived abandonment concerns, indicating the maintainers recognized stagnation perceptions and reasserted commitment. Growth appears driven by niche demand rather than viral adoption.
Adoption not verified through public evidence. Available via GitHub, Codeberg, IzzyOnDroid (F-Droid-compatible repo). Community channels exist (Telegram, Matrix groups) but member counts not disclosed. GitHub downloads metric mentioned in badges but not quantified in README. Active translation infrastructure (Weblate) suggests some international user base, but scale unclear.
Based on README, likely built as a Java-based Android app extending AOSP launcher foundations. Appears to implement modular theme system, gesture recognition layer, and widget framework. No detailed architectural documentation evident in README; implementation details not verifiable from metadata alone.
Not documented in README. No mention of test suites, CI/CD pipelines, or testing strategy.
Last push 2026-07-06 (3 days before evaluation date), indicating active ongoing work. README explicitly states project is not abandoned and mentions A16-based version in progress, suggesting maintainers are addressing Android 16 compatibility. However, slow issue/PR velocity may reflect small maintainer pool (README mentions two primary developers: Saul and Antonios).
ADOPT IF: You are an Android enthusiast seeking extensive customization (themes, gestures, icon organization) and value open-source licensing and community transparency. You are comfortable with smaller user communities and slower feature velocity. AVOID IF: You need guaranteed long-term stability or rely on commercial support; you expect rapid feature releases; you use a launcher primarily for productivity without deep customization. MONITOR IF: You are watching Android launcher ecosystem fragmentation and want to track whether small open-source projects maintain viability alongside commercial alternatives. Track the A16 update timeline and community growth as indicators of sustainability.
Independent dimensions
Mainstream potential
2/10
Technical importance
5/10
Adoption evidence
3/10
- Small maintainer pool (2 primary developers acknowledged) creates single points of failure and sustainability risk if contributors face personal/professional constraints.
- Likely lags behind Android OS releases; README mentions technical barriers on AOSP side and A16 work still in progress, suggesting reactive rather than proactive compatibility updates.
- Adoption metrics opaque; without download counts or user surveys, difficult to assess whether installed base is growing or atrophying.
- Long-term fragmentation risk: Android launcher market increasingly dominated by system defaults and commercial apps; niche open-source launchers may face declining relevance.
- Localization dependent on Weblate community; if translation momentum slows, international user onboarding friction may increase.
Neo Launcher likely remains a stable niche choice for Android customization enthusiasts but is unlikely to achieve mainstream adoption. If maintainers sustain A16+ compatibility updates and community engagement, the project can serve as a permanent alternative for users prioritizing open-source and modularity. Risk exists if maintainer availability wanes or Android ecosystem consolidates further around system launchers and closed commercial apps.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- Java
- License
- GPL-3.0
- Last updated
- 4d ago
- Created
- 73mo 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
[Feature Request] Icon design suggestions
[Feature Request] Button instead of gesture to open the app drawer
[Feature Request] Option to set folder background?
[Bug] User input (mostly) stops working
[Feature Request] app search filter when adding to folder/tab
Open pull requests
No open pull requests.
Top contributors
Similar repos
tanujnotes/Olauncher
Olauncher is a minimal, ad-free Android launcher designed to reduce screen time...
LawnchairLauncher/lawnchair
Lawnchair is a free, open-source Android home launcher based on Launcher3 that...
NeoApplications/Neo-Store
Neo Store is a modern F-Droid client for Android that replaces the default...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
NeoApplications/Neo-Launcher
this
|
2.1k | +4 | Java | 7/10 | 4d ago |
|
tanujnotes/Olauncher
|
3.7k | — | Kotlin | 7/10 | 5d ago |
|
LawnchairLauncher/lawnchair
|
13.1k | — | Java | 7/10 | 14h ago |
 Neamar/KISS
|
3.5k | — | Java | 7/10 | 23h ago |
|
NeoApplications/Neo-Store
|
4.8k | — | Kotlin | 7/10 | 3mo ago |
 ActivityLauncher/ActivityLauncher
|
1.8k | — | Kotlin | 7/10 | 21h ago |
Larger user base (13,072 stars vs 2,062); similar AOSP foundation and customization focus. Neo Launcher differentiates via dashboard feature and gesture-first design, but Lawnchair dominates in adoption and active community.
Comparable star count (3,450); KISS emphasizes minimal, search-focused interface. Neo Launcher offers richer visual customization and dashboard; different target user (power customizers vs speed-focused minimalists).
3,651 stars, Kotlin-based, minimal/zen aesthetic. Neo Launcher is feature-rich in contrast; targets different user psychology (customization vs simplification).
Neo Launcher competes less on replacing stock and more on offering niche features (theming, gestures, dashboard) for users willing to install third-party software.
Closed-source alternatives with larger user bases and feature parity. Neo Launcher's open-source nature and GPL-3.0 license appeal to privacy-conscious and customization-driven users; unlikely to capture market share from commercial apps.
