A mature Chinese-first desktop player with a changing future
LX Music Desktop is an Electron music application with 53,607 GitHub stars. Its README and linked documentation are Chinese-first, and the supplied material does not establish an English manual. It uses Electron 30+ and Vue 3, packaged for Linux, macOS, and Windows 7 or newer. The appeal is consolidation: music discovery, playlists, playback, shortcuts, and source selection in one desktop interface instead of several browser tabs or official clients.
Version 2.12.5 remains current, but LX Music is no longer the maintainers' main destination for new effort. The README directs users toward Any Listen, whose desktop and web editions reproduce most LX Music features and add WebDAV song playback, data synchronization, and independent playlists. Existing feature requests may be considered for that successor. LX Music is not abandoned, but the decision changes: adopt it for what works now, not for an ambitious future roadmap.
What happened when we ran it
Our run used commit abcbf5f in a fresh, unprivileged Debian container with Node 22, 3 CPUs, 8 GB of RAM, and no secrets. Installation succeeded in 32 seconds, bringing in 1,029 packages and consuming 386 MB on disk. The build completed in 152 seconds. For an 816-file TypeScript repository with about 76,973 source lines and a 25.7 MB checkout, that is a credible source-build result. The supplied log required no hidden credentials or manual recovery.
Testing is the weak part. The repository exposes no test script or target, so we skipped tests because there was nothing to invoke; that is not a passing suite. We also found no tests directory. An npm audit reported 12 known vulnerabilities: 6 high and 6 moderate, with no critical or low findings. There are 4 CI workflow files but no Dockerfile. Release automation exists, while the missing test target leaves application behavior less independently checkable than the successful build suggests.
The useful features go beyond basic playback
Cross-platform packaging is a real strength. Linux data follows $XDG_CONFIG_HOME/lx-music-desktop or the usual ~/.config path, macOS uses its Application Support directory, and Windows uses %APPDATA%. Since version 1.17.0, Windows users can place a portable folder beside the program to keep data there. That is practical for removable storage, controlled backups, or a machine where a conventional install is undesirable. The README also points to a FAQ, changelog, source-build instructions, and explanations of playlists and shortcuts.
The extension points make LX Music more interesting to technical users. Scheme URL support arrived in v1.17.0 and can hand actions from a browser to the desktop app, with a companion userscript offered by the project. A separate synchronization service has been available since v2.2.0 for users willing to operate a private server. Since v2.7.0, the app can start a local HTTP service exposing player-related interfaces to third-party software. These features make LX Music a controllable endpoint in a personal setup, not merely a closed desktop player.
The rough edges require informed consent
The project says its default settings and interface are not designed for beginners. It recommends reviewing settings, playlist behavior, and mouse and keyboard controls before regular use. That honesty is helpful, but the 53,607-star count should not be mistaken for universal approachability. Source setup was manageable on our box, yet daily configuration may demand more reading than mainstream clients. Users unable to read Chinese face extra friction where the app expects them to understand custom sources and non-obvious controls.
Source reliability is a hard boundary. LX Music says it does not obtain audio data; it passes song and artist information to the selected source and plays the returned online link. A link can be wrong or fail, and the application cannot verify its accuracy. The supplemental terms instruct users to remove generated copyrighted data within 24 hours, prohibit unlawful use, emphasize support for正版 releases, and describe the project as non-commercial research. Those terms sit alongside Apache-2.0 and say they prevail in a conflict, so redistribution or commercial use deserves legal review.
Current activity is strong, but support pressure is visible
The health signals are mixed. Release v2.12.5 landed on September 13, 2026, and the last push followed on September 14, so the repository is actively maintained today. Adoption is substantial at 53,607 stars. At the same time, 1,263 open issues represent a large maintenance queue. The evidence does not show response times or closure rates, so that count cannot prove poor support, but it should temper assumptions that every device, source, or platform problem will receive quick attention.
It fits as a personal desktop endpoint, not a managed streaming service
In a real stack, LX Music belongs on the user's machine, with the optional v2.2.0 sync server providing private playlist and data synchronization. Browser workflows can call it through the Scheme URL, while local tools can integrate through the v2.7.0 HTTP API. It is not evidenced as a catalog, rights-cleared streaming provider, containerized appliance, or team administration layer. If your music lives on a compatible personal server, Feishin may fit better; if you want the maintainer's forward path, Any Listen is the more strategic comparison.
The verdict favors capable existing users
LX Music earns its place through cross-platform packaging, portable data options, automation hooks, and a successful 152-second build in our lab. It is easiest to recommend to experienced Chinese-reading users who can judge custom sources, operate optional synchronization, and accept the project's legal conditions. The absent test target and 12 audit findings prevent an uncomplicated recommendation for security-sensitive environments. For a new deployment in 2026, compare Any Listen first; for an established workflow, v2.12.5 still looks actively maintained and useful.