How listen1/listen1_desktop works
Project type and purpose
• This is an Electron-based open-source desktop application (“Listen 1 音乐播放器”) that aggregates multiple online music services (网易云音乐, QQ 音乐, 酷狗, etc.) into one player.
• It uses Node.js/Electron to provide a cross-platform (Windows, macOS, Linux) desktop UI, plus a Chrome-extension submodule for shared search/play logic.
File structure
• Top level
• .github/workflows/release.yml: CI/CD for packaging & release
• package.json & package-lock.json: root-level scripts (npm run start/dist) and dependencies.
• LICENSE.md, .gitignore, .gitmodules: licensing, Git configuration, and the Chrome-extension submodule.
• app/
• main.js: Electron main process launcher & window management
• preload.js: Node→renderer secure bridge
• floatingWindow.html: a specialized mini-player window
• functions.js & listen1_chrome_extension (submodule): core music search & playback logic shared with the Chrome extension
• resources/: static assets
• package.json & package-lock.json: app-specific dependencies (Electron, IPC, UI libs).
• build/
README insights
• Describes multi-platform packaging (npm run dist[:platform]).
• Calls out the submodule initialization required for code completeness (git submodule update --init --recursive).
• Confirms Electron & build scripts, no backend server – all network calls go directly from the client.
Final advice
– Be exhaustive: map each JS file or module to its runtime component.
– Capture both runtime architecture (processes, data flow) and build/deploy workflow.
– Use layering to show OS, Electron, and network boundaries.