Tuneful: native music controls in the notch, menu bar or a mini player

What Tuneful actually is, and where the product lives

Tuneful is described as a native macOS playback manager that lets you control music from the notch, the menu bar or a mini player. The README's own framing is shorter: beautiful music controls for your Mac, native and lightning fast.

The key point about scope is in the features list. Tuneful brings native music controls for Spotify and Apple Music to your Mac. It is a control surface for streaming clients you already use, not a music player in its own right. That distinction determines what you can expect from it, and it is also why the topic list names `apple-music`, `spotify` and `music-player` alongside `macos-app` and `utilities`.

The second key point is where the product actually is. The top level of the repository contains only `.github/`, `.gitignore`, `README.md` and `docs/`. There is no source code, no build system, and no Swift package manifest. The README links to the Mac App Store for the download, and asks for a review there, so this repository is the project's public documentation and issue tracker rather than an open source codebase.

That is worth saying plainly rather than glossing over. The project listing records the licence as unknown and the primary language as unknown, and the topic tags mention Swift and SwiftUI, which is consistent with the README's claim that the app is built with Swift and SwiftUI, but there is no source in the repository to read. Anyone who wants to audit the code, fork it or self-host it will find nothing to work with, and the documentation describes a shipped product instead of a buildable one.

Three placements, and only one of them needs a notch

The interesting design decision in Tuneful is that it offers the same control surface in three different physical places, and you pick the one that suits your machine.

The notch player appears when you hover over your MacBook's notch, giving quick music controls and what the README calls satisfying haptic feedback. That is a MacBook-only feature in practice, since the notch is a piece of MacBook hardware, and the phrase in the README is carefully limited to your MacBook's notch.

The menu bar player shows what is playing and gives you the built-in playback controls from a customizable popover. This is the option that works on any Mac, and for a desktop user it is the default answer, since the menu bar is the conventional home for utility controls on macOS.

The mini player keeps a compact player on screen and lets you choose a style that suits you. This is the floating-window option for people who want the transport controls visible without hovering.

The README also says you can enable only the interfaces you want, alongside customizable notch, menu bar, mini player and keyboard shortcuts. That is the important word in this section, because a utility that occupies the notch, the menu bar and a floating window at once is a utility that fights for space on a screen that is already busy. The three-way choice is a real configuration decision rather than three features bolted together.

Favorites, scrobbling and Now Playing integrations

Beyond transport controls, the README lists a feature group for favorites and integrations: you can save songs from any player, and connect Spotify or Last.fm for scrobbling and Now Playing updates.

The phrase save songs from any player is broader than the rest of the feature list, and it is worth pausing on. If you can favourite a track from any player, the mechanism is not the app's own playback integration but something that reads the system's Now Playing information, which macOS exposes as a shared current-media state that any installed player can publish into. The same mechanism is what lets a menu bar utility display the title of whatever is playing, whether it came from Spotify, Apple Music or something else.

That reading is consistent with the way the app is positioned. It is a window onto the system media state, which is why the two named integrations are Spotify and Last.fm: Spotify is the source of the now playing information for one of the two supported players, and Last.fm is the destination for scrobbling.

Scrobbling is the feature that gives the utility a daily use beyond convenience. A scrobbler records what you listened to and when, in a service built for listening history. Doing that by hand is a chore most people give up on, and a menu bar button removes the friction. The Now Playing updates are the other direction, pushing the current track into a service that displays it.

The README does not describe the authentication flow for either service, nor whether scrobbling respects the Last.fm rules about how much of a track must play, so those details have to be checked in the app itself.

Installing it from the App Store rather than building it

There is no build path here, so the install story is short and worth stating precisely rather than dressing up.

The README's download link goes to the Mac App Store listing for Tuneful, and the project description names it as a native macOS app. The badge in the README points at the same listing, with a link to write a review there, which is a link an application that could be built from source would not normally include.

The `docs/` directory in the repository holds the images used by the README, including the icon, a download badge and the main `All.png` screenshot, so the documentation is published from the repository even though the code is not.

The feedback section is short: if you encounter issues or have feature requests, open an issue on the repository. That is the whole support model described. So the practical sequence for a new user is: find the app in the App Store, install it, choose which of the three interfaces to enable, connect Spotify or Last.fm if you want scrobbling, and use the issue tracker for problems.

For anyone hoping to build from source, there is nothing here. The repository has no code, no package manifest and no instructions for compiling it, so an evaluation has to be based on the app store listing and on running the shipped application.

Where Tuneful is the wrong tool

The first wrong-tool case is local music. The features list names Spotify and Apple Music, and the utility controls those players. If your library is FLAC files or a local library in a player like foobar2000 or a Plex server, there is no indication in the documentation that Tuneful can see them, and the app is not a player in its own right, so it cannot be the thing making noise.

The second case is a Mac without a notch and without a taste for menu bar clutter. The notch player is MacBook-specific, the menu bar player competes for space with everything else you have put there, and the mini player is a floating window you have to keep on screen. On a desktop, the app is one more utility in the top right corner, and a keyboard shortcut or a stream key may already cover it.

The third case is a team that needs to build on this. The repository has no source and no stated licence, so there is nothing to vendor, extend or self-host, and no guarantee that the app keeps working with the streaming clients it reads. A utility whose entire value depends on an undocumented integration with a third-party player's system integration is exposed to that player's changes, and you have no way to fix it yourself.

The alternative worth naming is the streaming client's own menu bar extra, since both Spotify and Apple Music ship their own macOS controls. The difference in approach is that a built-in extra knows about its own client perfectly and adds no second process, while a third-party utility like this one gives you a consistent surface that works across both players, adds Last.fm scrobbling that neither client does, and offers the notch placement and the mini player that neither client provides. You trade a little indirection and a little extra process for that consistency.

Maintenance state and what the repository can and cannot tell you

The last push to the default branch was on 2026-10-06, and the repository is not archived, so something is still being updated. The repository has no GitHub releases, which is expected when the distribution channel is the Mac App Store rather than a binary release page, since the store handles versioning and updates.

What the repository can tell you is narrow but real. It tells you the product exists, what the three interfaces are, which players are supported, that the app is written with Swift and SwiftUI, and that it is intended to use minimal system resources. It tells you how to get it and where to report problems.

What it does not tell you is most of what an adoption decision usually needs. There is no stated minimum macOS version, no pricing information, no list of what happens on a free tier of either streaming service, no privacy statement, and no explanation of how the Spotify connection is made, for instance through the Mac media API or through a Spotify developer application. The project description also carries no licence and no primary language, which is consistent with a repository that holds documentation rather than code but leaves the legal position on the code unstated.

The macOS version requirement is worth checking before you buy. The notch player, the media state integration and the SwiftUI interface all imply a recent system, and the app store listing is where that will be stated.

So the honest assessment is that this is a well-scoped native utility with a sensible three-way placement model, whose repository is its documentation, and whose evaluation has to happen on the App Store page and in the running app rather than in the source.

Editorial conclusion

Adopt Tuneful if you play music from Spotify or Apple Music on a Mac and want a small, native control surface instead of switching to the streaming app, and if you scrobble to Last.fm. Do not adopt it expecting a general audio player, since it controls existing players rather than playing local files, and do not expect the source, because the repository contains only the README and documentation images, with the distributed app coming from the Mac App Store. Before you buy it, check the App Store listing for the current price and the minimum macOS version, since neither is stated here, and confirm that the Spotify and Apple Music integrations on your plan support the Now Playing control the app relies on.

Frequently asked questions

Official sources

1. Issues
2. martinfekete10/Tuneful on GitHub
3. Project website
4. README