Using Bandcamp as a real Mac app: the same place at home and on the road

Wanting a Bandcamp desktop app is rarely about features. It is about the collection page being a browser tab that gets closed by accident halfway through a record, about Cmd+Tab landing on a research window instead of the music, and about the laptop on the road being set up differently from the machine at home. Bandcamp solved the phone side years ago and never shipped the desktop equivalent. That leaves a gap that can be closed, but only once it is clear what Bandcamp publishes and what it does not.

What Bandcamp publishes, and where it stops

Bandcamp's own site answers this in the footer rather than on a marketing page. The two app links there point to the listing on Google Play and the listing on the iOS App Store. There is no third link, no disk image, and no page offering a Windows or macOS installer. The mobile app is referred to throughout the help centre as the Bandcamp app, and the platform pairing is stated plainly in the article on offline listening.

You can listen to the items in your collection when you're offline by downloading them in the Bandcamp app for Android or iOS. Source: get.bandcamp.help

The same article goes on to describe what a computer is for in Bandcamp's model, and it is worth quoting because it is the opposite of what most streaming services assume. Listening to a purchase in a different player means downloading the files to a computer in any format and syncing them from there. The computer is treated as the place where files land, not as a place where an app runs.

That is the whole shape of the situation. On a Mac, Bandcamp is a website with a full player in it, plus a download button that produces real files. Everything the phone app adds, offline caching in particular, exists because a phone cannot be trusted to have a network. A Mac with a browser already has the player and already has a filesystem.

The iPhone app on an Apple silicon Mac

There is one route that sits between the website and nothing, and it is easy to miss because Bandcamp does not advertise it. The App Store listing for the Bandcamp app is published by Bandcamp Ventures, LLC, and its compatibility section names more than the phone. It lists iPhone with iOS 16.6 or later, Apple Vision with visionOS 1.0 or later, and Mac with macOS 12.0 or later on a Mac with an Apple M1 chip or later.

That last line means the iPhone build can be installed and run on Apple silicon Macs. It is genuinely useful for one thing: offline downloads, which the website does not offer as a cache. It also comes with the constraints of an iPhone app running on a desktop. The layout is a phone layout, the window resizes awkwardly, Intel Macs are excluded entirely, and the parts of the experience that feel native on a Mac, such as a wide two column collection view, are not there because they were never designed.

The practical reading is that this route suits a specific person: someone on Apple silicon who wants a copy of the collection available on a plane. For daily listening at a desk, the website's player is the better interface, and the problem to solve is not the interface but the window it lives in.

Why the search results are full of unofficial installers

Searching for this leads quickly to three kinds of page that are not Bandcamp, and telling them apart saves time.

The first kind is a community project on a code hosting site, typically an Electron shell around bandcamp.com maintained by one person. Some are well kept and some stopped years ago. The thing to check is the date of the last commit and whether the release notes mention a recent macOS version, because an abandoned shell keeps an old browser engine inside it and that is where security problems live.

The second kind is a catalogue site that lists thousands of services and offers a wrapper for each. These are real products, but the page is generated from a template, so a listing for Bandcamp is not evidence that anyone tested Bandcamp's player in it. The test is still the one to run for a day.

The third kind is a download portal with a title like "Bandcamp for PC, Mac and Windows", which repackages the Android app with an emulator or simply serves an installer of unclear origin. Nothing on Bandcamp's own site points to any of these, and a music account with a stored card in it is not the place to experiment. Anything asking for a Bandcamp password outside a window pointed at bandcamp.com deserves refusal.

Three routes to a Bandcamp window

Once the goal is stated as a window rather than an app, the options are short and the differences are concrete.

Route	Setup	Reachable by Cmd+Tab	Offline copies	Good fit for
Browser tab	None	No	Downloaded files only	Occasional listening
Safari, Add to Dock	Two clicks in Safari	Yes	Downloaded files only	One account, no installer wanted
iPhone app on Apple silicon	App Store install	Yes	Yes, in the app	Offline listening away from a network
Site to app tool	Pick the URL, build once	Yes	Downloaded files only	A window that matches the rest of the Dock

Safari's route is documented by Apple and appears in the File menu as Add to Dock on macOS Sonoma 14 and later. The result has no tab strip and no address bar, and it keeps its own cookies and website data separately from Safari, which is why a second account can live in a second window without either one signing the other out.

Chrome offers a comparable step under the three dot menu, in Cast, save and share, then Install page as app. Chrome's help page is clear about what such an app is and what it can gain.

A web app is an app built for the web that you can access on any device. You can use web apps to have a website work as an app and access it on your computer or mobile devices through the launcher or home screen. Some web apps include extra features, like more storage to browse content offline, notifications, file system access, and icon badges. Source: support.google.com

The caveat with Chrome is that the resulting app inherits the profile it was created from, so it opens whichever Bandcamp account that profile is signed into.

The same place at home and on the road

The part that makes a window worth building is consistency, and it is the reason this matters more for music than for most web tools.

A Bandcamp collection lives on the server, so any machine signed in sees the same records in the same order. What differs between machines is everything around it: which browser is default, how many tabs are open, whether the window is the fourth or the fourteenth in the switcher. A listening window is a habit, and habits break when the gesture changes. The same icon in the same Dock position on the desktop at home and the laptop in a café means one gesture works in both places, and the record that was playing is found by muscle memory rather than by searching.

There is a second, quieter benefit. A dedicated window is not a browsing window, so it does not accumulate the twelve tabs that make the browser slow and the fans loud. Playback keeps running when the research browser is quit, which is the single most common way a record stops halfway through. Anyone who keeps one window for listening and one for work will recognise this as the actual problem being solved. The general shape of what a dedicated window covers is on the Features page.

Downloads are the part that no window replaces

A Bandcamp purchase is a file, and this is the detail that separates Bandcamp from subscription services. The help centre's guidance is to download purchases to a computer and take them from there, in whatever format suits, and the format list includes lossless options alongside MP3. Those files are not tied to the window they were bought in.

That has a consequence for how to set things up. A dedicated window is the right place to browse, buy and stream. It is not a library manager, and pretending otherwise leads to a folder of unsorted zip files in Downloads. The workable arrangement is two places rather than one: the window for the collection and for new releases, and a local player pointed at a music folder for the records worth keeping close. Purchases downloaded once can be kept in sync between machines by whatever file sync is already running, which is what makes the home and road setups match on the file side as well as the window side.

Anyone reaching for a download because the network is unreliable should compare that against the iPhone app on Apple silicon first. Caching inside an app needs no folder structure and no decisions about format, and for travel it is less work than managing files by hand.

What to test before the browser tab is closed

Three things are worth checking for a day, because they are the ones that send people back to the tab.

The first is playback continuity. A window that pauses when it loses focus, or that stops when the Mac sleeps and does not resume, is worse than a tab. Play a full album while working in another app and see what happens at the track boundaries.

The second is the keyboard and the media keys. Play and pause from the keyboard, and the Now Playing control in the menu bar, depend on the page exposing its playback state to the system. Whether that works is a property of the site and the container together, so it has to be tested rather than assumed.

The third is signing in. Bandcamp sign-in arrives by email link for many accounts, which means a link opening in the default browser rather than inside the window. That is a one time nuisance if the session persists afterwards, and a daily nuisance if it does not. Checking whether the window is still signed in the next morning settles it. Cost and account limits for tools that build such windows are set out on the Pricing page.

What to change first

Build one window for Bandcamp, put it in a fixed Dock position with Kagemusha or with Safari's Add to Dock, and play one full album through it before deciding anything else. If travel is the real problem rather than tabs, install the iPhone app on an Apple silicon Mac instead and cache the records that matter.