egoist/mygo-cloudmusic

Media & Design

A third-party NetEase Cloud Music desktop client with a native UI and no WebView, aimed at listeners who want lyrics and Hi-Res playback without a browser engine.

110
17
Go
AGPL-3.0
1 day old

A native desktop client for one streaming service, built on a small Go UI framework. Worth a look if you use NetEase Cloud Music on desktop and dislike the web-app feel; read the build requirements before downloading anything.

The problem

You want to listen to your NetEase Cloud Music library on a desktop without a Chromium-based shell, and you want the small things a music player should do: keep your queue after a restart, show word-by-word lyrics with translations, and give you a seek bar that does not crackle. The client changes those steps directly: you scan a QR code to log in, the session is stored in the system credential store, and the queue and playback position are restored the next time you open it. The result is a desktop player that behaves like a local app rather than a wrapped web page.

What's different

The distinguishing choice is the rendering stack. This is written in Go on MyGo, the author's native UI framework, and the README explicitly states there is no WebView. Everything from the daily recommendations and private FM to the comments and the word-by-word lyrics page is drawn natively. Playback is also handled with more care than a typical wrapper: tracks stream while downloading, the README lists standard through Hi-Res quality including FLAC, and played songs are cached locally so replay starts instantly. Volume leveling and fade-out/in on pause and resume are also listed.

The trade-off is that the client inherits the framework's constraints. You are not installing a packaged release described in the README; you build it yourself with go tool mygo dev or go tool mygo build. That makes this a project for people comfortable with a Go toolchain, not a double-click app for casual users. The interface style also follows MyGo rather than the official client, so anyone expecting the exact official layout will need to adjust. Platform coverage is not spelled out in the supplied README, so check the project page before assuming your OS is supported.

Who should try it

A good fit is a developer who already uses NetEase Cloud Music, cares about lyrics and Hi-Res audio, and is willing to build a Go application to get a native-feeling player on desktop. The queue restore and local cache matter most to people who listen in long sessions and reopen the app daily. A poor fit is someone who wants an installable client they can hand to a non-technical family member, or who needs a documented list of supported operating systems before committing. The README credits NeteaseCloudMusicApi as the reference for eapi encryption and the login flow, and folia-major for the lyric animation effect; those are implementation references, not bundled components you configure.

Requirements and limitations

The build path requires Go 1.27+ per the README, plus the MyGo toolchain invoked through go tool mygo. That is a meaningful gate: there are no documented prebuilt binaries or package-manager installs in the supplied material, and the build output goes to build/. Login depends on scanning a QR code, and the session relies on the system credential store, so the app expects a desktop environment that provides one.

The project is also explicitly unofficial and states that music copyright belongs to the respective rights holders, so availability of songs and account features follows the service, not this client. The license is AGPL-3.0, which matters if you plan to redistribute a modified build. Ongoing upkeep is mostly about keeping the Go toolchain and MyGo in step with the source, since the README gives no upgrade or recovery guidance.

HotRepo's take

HotRepo first recorded this repository at 1 day old, with 110 total stars and #3 on the NEW-REPOSITORY board on 2026-10-26; that is a snapshot, not a growth measurement. There is no comparable daily-board history, so persistence cannot yet be judged. Before investing build time, verify on the project page which desktop platforms are supported and whether prebuilt packages are offered.

Written by AI from the project's README, updated October 26, 2026. The project's own docs are the source of truth.