Beans Music bundles no music sources, and its Xcode project is generated rather than committed
Beans Music: a third-party iOS 26 Liquid Glass style music player, for learning purposes only.
At a glance
- What is it?
- Beans Music is an open-source SwiftUI player for iOS 15 and later that browses NetEase Cloud Music, QQ Music, and Kugou from one interface. Two things about the repository are worth knowing before you build it: the music sources are yours to supply, and the Xcode project comes out of a project.yml rather than sitting in the tree.
- Who is it for?
- Beans Music is worth trying if you already have music sources to plug in and a Mac with a current Xcode, because the player surface is unusually complete for a third-party app: lyrics with translation and interactive seeking, several player layouts, an equalizer, background playback, lock-screen controls, and a sleep timer. It is a poor fit if you expected a signed build from the release page or a set of working sources out of the box, since neither is here.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 25 days ago.
- What is it written in?
- Mainly Swift, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- XIaodou0416/Beans-Music477 ★ · +110
| Repository | 2026-09-17 | 2026-11-15 |
|---|---|---|
| XIaodou0416/Beans-Music | 367 | 477 |
110 Stars in the last 59 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The app ships with no music sources and expects you to bring your own
The most consequential line in the development notes is short: user-configured music sources are stored locally and are not bundled with the repository. So a fresh clone is an empty player. The highlight list does mention importable music sources, which is the intended path in, but nothing playable arrives with the source tree and there is no demo catalogue to fall back on while you work out the import.
What the app does cover is broad. It browses and searches NetEase Cloud Music, QQ Music, and Kugou Music. With an account it brings in synced playlists, favorites, rankings, artists, albums, and recent plays. The playback surface includes a queue, shuffle, repeat, playback speed, a sleep timer, background playback, and lock-screen controls. Lyrics come with translation, appearance controls, scrolling, and interactive seeking. There are multiple player layouts, Liquid Glass styling on supported systems, themes, wallpapers, and equalizer controls, plus local playlists, offline files, native share and export flows, and Chinese and English localization.
The three platform names in that list are not equally represented in the code layout. NetEase and QQ Music each get a named API file, while the visible file listing stops there, so the Kugou integration has no file named in the layout as published.
The project file is generated, so Xcode alone is not enough
There is no .xcodeproj in the repository. There is a project.yml at the root, which is an XcodeGen specification, and the build requirements are macOS, Xcode 26 or later, and XcodeGen. That ordering matters: a contributor cloning the repository has an Xcode project to generate, not one to open, and a machine with an older Xcode cannot satisfy the stated floor.
The documented path is three commands. Install the generator, generate the project, then build with signing switched off:
brew install xcodegen
xcodegen generate
xcodebuild \
-project Beans.xcodeproj \
-scheme Beans \
-configuration Release \
-sdk iphoneos \
-derivedDataPath build \
CODE_SIGNING_ALLOWED=NO \
CODE_SIGN_REQUIRED=NO \
CODE_SIGN_IDENTITY="" \
buildAll three code-signing knobs are turned off, which is what makes the command work unattended on a machine with no signing identity. The scheme name and the project name both come from the generated spec, so renaming anything means editing project.yml and regenerating rather than editing the project in Xcode's interface, which would be overwritten on the next run.
The result is described as an unsigned app, and the visible file does not walk through a signing or sideloading step, so treat the output of that command as something to sign yourself before it goes on a device.
The workflow builds an unsigned IPA and stops short of publishing
Continuous integration exists, and it is deliberately short of a release. The GitHub Actions workflow can build an unsigned IPA on demand, it is configured for test builds by default, and it does not create a release unless it is explicitly enabled. That is a coherent choice for a project whose repository description marks it as for learning, but it means there is no signed artifact to download.
The distribution picture matches. There is exactly one tagged release, v1.6.6, published on 2026-09-06 and titled with the app name and version rather than a bare tag. There is no homepage set, so the repository page is the only place the project is presented. The root also carries a CHANGELOG.md and a separate FEATURES.md, which is an unusual pairing and suggests the feature list is maintained separately from the release history rather than derived from commits.
A ci-logs directory sits at the repository root, so build logs are kept inside the tree rather than only in the Actions interface. That is convenient for reading a failed build without leaving the repository, and it is also the kind of directory that tends to grow, which is worth knowing before you decide how to organise your own fork.
The deployment floor is iOS 15 while the styling targets iOS 26
Two version numbers in this project point in opposite directions, and both are real. The README describes an open-source SwiftUI music player for iOS 15 and later, which is the deployment target. The repository description presents it as an iOS 26 Liquid Glass style third-party player, which is the visual identity. The highlight list reconciles them with a qualifier: Liquid Glass styling on supported systems.
That qualifier is the whole story. The glass effect appears where the operating system provides it and the rest of the appearance layer carries the app elsewhere, which is what the themes, wallpapers, and equalizer controls are for. So the styling is a progressive enhancement rather than a requirement, and reading the description alone would give the wrong idea about how far back the app runs.
The build toolchain is the other version constraint and it is not the same one. Xcode 26 or later is needed to compile, regardless of the iOS 15 deployment floor, so the practical requirement is a recent Mac and a recent Xcode rather than flexibility about the phone. Separating those two numbers is the first thing to get right, because it decides whether you can build at all and it has nothing to do with which device the app will run on.
One file owns the queue and the API files own the networking
The published layout is a short file list, and the descriptions are the design summary:
Beans/
BeansApp.swift Application entry point
RootView.swift Tab navigation and mini player
DiscoverView.swift Home, recommendations, and rankings
SearchView.swift Platform search and result navigation
LibraryView.swift Synced and local music libraries
ProfileView.swift Account, appearance, backup, and settings
PlayerView.swift Full player and lyrics experience
PlayerManager.swift Queue, playback, history, and recovery
NetEaseAPI.swift NetEase integration
QQMusicAPI.swiftTwo structural choices stand out. RootView owns the mini player, so playback follows you across the tab navigation rather than living inside one tab. PlayerManager is described as owning queue, playback, history, and recovery together, which puts interruption recovery in the same place as the queue rather than scattered across the player view, and that is what background playback and lock-screen controls have to be built on.
The development notes add the rule that keeps this tidy: the project uses SwiftUI and keeps platform-specific networking inside the corresponding API files. The listing ends at QQMusicAPI.swift with no description, and the file list is not presented as exhaustive, so the size of the codebase cannot be judged from it. A viewer or an audio component is not named in the visible layout at all.
The star history badge at the bottom points at a different repository
The last block in the README is a star history chart, and it does not point at this project. The embedded image URLs reference jiajia2222/Moumusic, with the repository parameter and the query string both naming that other project, for both the dark and the light colour schemes. Whatever growth the chart shows is that repository's history, not Beans Music's, and the mismatch sits in the last thing a reader sees.
It is the kind of leftover that survives a fork or a rename, and it is worth correcting if you maintain a copy, because a reader who trusts the chart draws a wrong conclusion about how active the project is. The same caution applies to the single release tag and to the changelog: with one release visible, the release history is too thin to support any claim about cadence.
Two other details round out the repository. Alongside the English README there is a docs directory and a file with a Chinese name, so the documentation is bilingual without the Chinese file being translated in place. The licence is MIT, and the notice underneath it is the part that matters for this kind of app: music, trademarks, and platform services belong to their respective owners, and using the app responsibly means following each platform's terms of service. The repository description also marks the project as for learning, which is the framing to keep in mind when deciding what to do with it.
Editorial conclusion
Beans Music is worth trying if you already have music sources to plug in and a Mac with a current Xcode, because the player surface is unusually complete for a third-party app: lyrics with translation and interactive seeking, several player layouts, an equalizer, background playback, lock-screen controls, and a sleep timer. It is a poor fit if you expected a signed build from the release page or a set of working sources out of the box, since neither is here. Before you invest an afternoon, check three things yourself: that you can supply sources yourself, since they are stored locally and deliberately not in the repository; that you can meet the toolchain, which needs macOS, Xcode 26 or later, and XcodeGen before any code compiles; and that you are comfortable with an unsigned build, because the documented command disables signing and the workflow is set to test builds rather than releases.
Frequently asked questions
What is Beans Music and which music platforms does it browse?
Beans Music is an open-source SwiftUI music player for iOS 15 and later that brings several music platforms into one native app. It browses and searches NetEase Cloud Music, QQ Music, and Kugou Music, and with an account it covers synced playlists, favorites, rankings, artists, albums, and recent plays.
Do I need to supply my own music sources to Beans Music?
Yes. User-configured music sources are stored locally and are not bundled with the repository, so nothing playable ships in the source tree. Importable music sources are listed among the features, which is the intended way to add them.
How do I build Beans Music from source?
You need macOS, Xcode 26 or later, and XcodeGen, because the Xcode project is generated from a project.yml at the repository root rather than committed. Run brew install xcodegen, then xcodegen generate, then the xcodebuild command that disables code signing to produce an unsigned app.
Does the Beans Music release pipeline sign and publish the app?
No. The GitHub Actions workflow can build an unsigned IPA on demand, and it is configured for test builds by default and does not create a release unless explicitly enabled. The only tagged release visible is v1.6.6, published on 2026-09-06.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/xiaodou0416-beans-music)Star history chart for your README
[](https://hysenlabs.com/projects/xiaodou0416-beans-music)Was this useful?