Basecamp in its own window, with notifications that work

Searching for a Basecamp desktop app usually starts with a specific annoyance. Basecamp is open in a browser tab somewhere behind eleven other tabs, a ping arrived an hour ago and nobody saw it, and Command+Tab does not get there because Basecamp is not an application as far as macOS is concerned. The good news is short: 37signals publishes a real Mac app, and it is a free download. The rest of this page covers what that app does, what it does not do, and which of the other routes is worth taking when the official installer is not the right answer.

The official Mac app exists, and that is the first thing to try

37signals lists every way to reach Basecamp on a single page at basecamp.com/via: iOS, Android, Mac, Windows, the web, and a command line interface. The Mac download is a standard disk image served straight from basecamp.com, and the help documentation splits it into two builds so the right one lands on the right machine.

Available on Mac and Windows. Download the version for your system and run the installer: Basecamp for Windows, Basecamp for Mac (Apple silicon), Basecamp for Mac (Intel). Source: basecamp-help.com

If the chip is unclear, the Apple menu and About This Mac will say. Anything reported as M1, M2, M3 or newer takes the Apple silicon build. Anything reporting an Intel processor takes the other one. Downloading the wrong one is not destructive, it simply will not be the fast version, and on Apple silicon an Intel build runs through translation.

This matters because most articles about turning Basecamp into a desktop app were written before the app shipped, or were written about a different product entirely. A good share of the search results for this query are about Garmin BaseCamp, which is mapping software for GPS devices and has nothing to do with project management. Checking the vendor page first saves an hour of chasing workarounds for a problem that already has a supported answer.

What the official app changes, in practice

The desktop app is not a bookmark with a nicer icon. Three things change the moment it opens.

Notifications become macOS notifications. Pings and mentions arrive through the system notification centre rather than through a browser permission prompt, which means they obey Focus modes, appear in the notification list, and can show a count on the Dock icon. A browser tab can do some of this, but only while that browser is running and only if the site permission was granted in the first place.

The second change is window behaviour. The app holds a place in the Dock and in the Command+Tab switcher, so getting back to it is one gesture instead of a hunt through tab strips. The third is tabs inside the app itself. Basecamp's own documentation describes opening several projects, messages or to-do lists side by side without losing the current position, which is the part a single web app window cannot reproduce.

There is one more detail worth knowing before installing, because it changes how account switching feels. From the same help page: "If you have multiple accounts, you'll install the Basecamp app just once. To switch between accounts, type the account name in the Jump/Search bar, or go to your profile picture, then Account & Settings." The switch happens inside one window. That is convenient for people who move between a client account and an internal one occasionally, and it is a real constraint for people who need both visible at once.

The routes available, side by side

Four routes reach the same Basecamp. They differ in what they cost to set up and what they give back.

Route	Setup	Notifications	Separate login store	Good fit for
Browser tab	None	Browser permission, browser must be open	Shares the browser session	Occasional access
Official Mac app	Download and install a .dmg	System notifications	Shares nothing with the browser	Most people, most of the time
Safari, Add to Dock	Two clicks in Safari	System notifications, badge on the Dock icon	Own cookie store, separate from Safari	macOS Sonoma 14 and later, no installer allowed
Chrome, Install page as app	Two clicks in Chrome	Through Chrome, which must be running	Shares the Chrome profile it was made in	People already living in a Chrome profile

Apple documents the Safari route directly. The File menu carries an Add to Dock item from macOS Sonoma 14 onward, and Apple is explicit that the result is walled off from the browser it came from: browsing history, cookies, website data and settings are not shared with Safari. That isolation is the interesting property, and it is the reason the same trick can hold a second identity for the same service.

Chrome's equivalent sits under the three dot menu, in Cast, save and share, then Install page as app. Chrome's own help page describes installed web apps as sites that behave like apps with launcher access, extra storage, notifications and icon badges. The trade is that the resulting app inherits the Chrome profile it was created from, so the account it opens is the account that profile is signed into.

Notifications, and the three places they break

A notification has to survive three checkpoints before it reaches a human, and Basecamp only controls the first one.

The first checkpoint is Basecamp's own settings. Every person has notification preferences on their profile, and Basecamp respects working hours if they are configured, holding pings until the next working morning. Someone who set that up months ago and forgot will conclude the app is broken when the app is doing exactly what it was told.

The second checkpoint is macOS. System Settings, then Notifications, then the application in the list. An app that is not allowed to post notifications will never post one, and a Focus mode can silence an app that is otherwise allowed. Both are per application, which means installing the desktop app after living in a browser tab creates a new entry in that list that nobody has approved yet. Approving it once is the whole fix.

The third checkpoint is whether the process is running at all. This is where browser based routes differ from the installed app: a Chrome web app depends on Chrome, and Apple's Safari web apps and the official Basecamp app can be added as login items so they start with the machine and keep listening. For anyone who installed a desktop app specifically so that pings stop being missed, the login item step is the one that actually delivers it.

When a separate app still makes sense

The official app covers the common case. Three situations sit outside it.

Two accounts open at once. A contractor working in a client's Basecamp and their own agency's Basecamp gets one window and a switcher, not two windows. Anything that shows both at the same time has to keep two separate cookie stores, which is what Safari web apps and a site to app tool for macOS both do. Two icons, two logins, no switching.

Installers that IT will not allow. Managed laptops often block disk images from outside an approved catalogue. The Safari route needs no installer at all, because macOS builds the app locally from the page that is open.

A shelf of work sites, not one. Basecamp is rarely the only web tool in a day. Once the list includes a ticket system, a wiki, a payroll portal and a shared inbox, installing whichever of them happen to ship a Mac binary leaves the rest in tabs. Making the whole set consistent is the argument for a general tool rather than one vendor's app. A description of what that kind of tool covers is on the Features page, and the list of services already prepared as presets is on the Supported services page.

Two routes that are not a window at all

The page that lists the desktop downloads also lists two ways of working that never open Basecamp in the first place, and for some jobs they beat any icon in the Dock.

The first is email. 37signals states plainly that most Basecamp notification emails can be answered from the inbox, and the reply lands in the thread it came from. For a manager whose only daily contact with a project is approving things and answering questions, that removes the window problem entirely. The catch is that email replies are plain replies: assigning a to do, attaching a file to a specific card or moving a due date still needs the real interface. Treating email as the default and the app as the place for actual edits is a workable split, and it explains why some teams never feel the need for a desktop app at all.

The second is the command line. Basecamp publishes a CLI, hosted on GitHub under the basecamp organisation, that reaches projects, to dos and messages from a terminal. That is a narrow audience, but it is the right tool for one specific pattern: scripted updates, such as posting a build result into a message board or closing a to do when a deploy finishes. Anyone who has been keeping a browser tab open purely to paste status updates by hand should look at this before installing anything.

Both routes also answer a question the desktop app cannot. A tab, a web app and a native app all still require someone to look at a screen. Email and scripts do not, and the fastest way to stop missing pings is sometimes to stop needing to watch for them.

Removing what did not work

Cleaning up is worth doing before layering a second approach on top of the first, because two Basecamp icons in the Dock that behave differently will cost more time than either route saves.

The official app uninstalls like any Mac application, by dragging it out of the Applications folder. A Safari web app is removed from the same place, since Apple stores it in the Applications folder inside the home folder. A Chrome web app is removed from inside Chrome: open chrome://apps, right click the icon, then Uninstall. Signing out first is the polite version, and it also clears the stored session so a later reinstall starts clean.

One caveat applies to all of them. Removing the app does not change notification preferences held in a Basecamp profile, so a person who muted everything during a busy week and then reinstalled will still hear nothing. That setting lives on the account, not on the machine. The Guide covers the same checks for other services that behave this way.

What to change first

Download the official Basecamp app from basecamp.com/via, pick the build that matches the chip, and approve its notifications in System Settings the first time one is offered. Add it as a login item if missed pings were the reason for the search. If two accounts need to be visible side by side, or if Basecamp is one of six work sites living in tabs, set the whole shelf up the same way with Kagemusha instead of installing them one vendor at a time.