Notion in a window of its own, next to everything else

Searching for a Notion desktop app for Mac has an unusually clean answer: it exists, it is free, and Notion publishes it. That is where most articles on the subject stop, which is a shame, because the download is the easy part. The harder question is what changes after installing it, and why the same person who installs the Notion app usually still has nine other work sites living as browser tabs an hour later.

The desktop app is worth having. It is also worth understanding what it actually does, because the benefit is not the one most people expect, and the pattern it demonstrates applies to every other tool in the tab bar.

Which build to download, and what it requires

Notion's download page offers three macOS builds: a Universal build, an Apple Silicon build, and an Intel x64 build. Universal contains both architectures and runs correctly on either kind of Mac, which makes it the safe default when there is any doubt. The architecture specific builds are smaller. On an M series Mac the Apple Silicon build and the Universal build behave identically, so the only reason to pick one over the other is disk space.

The requirement that matters more is the operating system. Notion's own system requirements page states macOS 12 or above. That single line decides the question for a lot of people before any comparison starts. A Mac still running macOS 11 or older cannot install the current desktop app, and the answer there is not a different download, it is the browser.

That threshold is not unique to Notion. It has become the common floor across the tools people keep open all day, and it is worth seeing the numbers next to each other.

Application	Minimum macOS
Notion desktop	macOS 12 or above
WhatsApp Messenger	macOS 12.1 or later
Slack for Desktop	macOS 13.0 or later
Google Chrome	macOS 13 Ventura and up
Safari web apps, Add to Dock	macOS Sonoma 14

The pattern is that the floor keeps rising, and it rises for the browser as well. A Mac that cannot run the Notion app today is often one or two releases away from not running the current Chrome either, which changes what the realistic options are.

What the desktop app actually fixes

Notion describes the desktop app as offering a clean interface without the temptation of browser tabs. In practice the significant differences are narrower and more concrete than that phrasing suggests.

The first is offline access, and it is the real reason to install the app. Notion's offline mode runs on the desktop and mobile apps and does not run in a web browser at all. Pages are made available offline individually, through the three dot menu at the top of a page and the Available offline toggle, and a progress bar shows the page downloading to the device. Everything that has been downloaded is listed under Settings then Offline. On the Plus, Business and Enterprise plans, recently visited and favorited pages download automatically, and that automatic behaviour can be switched off in the same settings panel.

The limits are specific and worth knowing before relying on it. Downloads are per device, so pages made available on a phone are not available on a laptop. Subpages of a downloaded page do not come along automatically, so a project page with ten child pages needs those children downloaded individually. And while offline, a page cannot be shared and its permissions cannot be edited.

The second difference is notifications. The desktop app delivers push notifications for mentions, task assignments and reminders through macOS rather than through a browser permission prompt.

The third is smaller than it sounds. The app has its own tab system, with hover previews of the page inside each tab, and a Command Search that opens on a customisable keyboard shortcut. This is genuinely faster than the browser equivalent. It is also, unavoidably, tabs. The app removes Notion from the browser's tab bar and gives Notion a tab bar of its own.

What the desktop app leaves untouched

Here is the situation an hour after installing it. Notion has a Dock icon, a Command-Tab entry, and offline pages. Good. The browser still holds a calendar, a mail interface, a ticket tracker, a design tool, a CRM, a dashboard for something internal, and two documentation pages. Nothing about that changed.

This is the part that gets skipped. Installing one official app improves one tool. It does not address the shape of the problem, which is that a modern working day runs on ten or twelve web services and only two or three of them happen to ship a Mac application. The ones that do ship an app are usually the largest companies, which means the tools that get rescued from the tab bar are selected by vendor size rather than by how often they are used. An internal admin panel opened forty times a day stays a tab. A note taking app opened four times a day gets an icon.

There is a second gap for anyone who works across more than one account. Two Notion workspaces, or a personal account and a client account, share one browser session unless a second browser profile is created. The official app does not turn that into two windows either.

Giving every site the same treatment

The general version of what the Notion app does is available for any site, and two of the three routes are already installed.

Safari has it built in, starting with macOS Sonoma 14. Open the page, choose File then Add to Dock, and name it. Apple's documentation describes exactly what results: the web app is saved to the Applications folder of the home folder, and it shares no browsing history, cookies, website data, or settings with Safari. For sites that send notifications, the Dock icon can show an unread count. Opening the app and choosing Settings from the menu bar allows the name, the URL and the icon to be changed.

Chrome has a similar option, reached through the More menu, then Cast, save, and share, then Install page as app. It produces a separate window with its own Dock entry, though the menu item is not offered on every site.

A dedicated site to app tool covers the cases those two leave open. It builds each site as a standalone application rather than as a browser attachment, keeps cookies and login sessions isolated per app so two accounts can be signed in at once, allows the browser engine underneath to be chosen, and repairs the app after the underlying browser updates. The Features page sets out which of those apply per app.

Route	Cost	Separate logins per app	Notes
Official vendor app	Free where it exists	Depends on the vendor	Only available for sites whose vendor ships one
Safari, Add to Dock	Included with macOS	Yes	Requires macOS Sonoma 14 or later
Chrome, Install page as app	Included with Chrome	Per Chrome profile	Menu item is not offered on every site
Site to app tool	Free tier, paid tier for more apps	Yes	Works on any site, including internal admin panels

Three things to check after a site leaves the browser

Moving a site into its own window is quick. The friction, when there is any, shows up in the same three places every time, and all three are easier to handle on day one than on day four.

The first is notification permission. A separate window means a separate cookie store, and notification permission is granted per origin per store. The permission granted to a site inside the browser does not travel with it. The new app starts with nothing granted, so the site's own notification setting has to be turned on again inside the app, and the macOS prompt accepted when it appears. Skipping this produces the most common complaint about any standalone web app, which is that it stopped notifying, when in fact it was never asked.

The second is signing in. Services that authenticate through a provider open a separate sign-in window, and that flow behaves differently depending on what is underneath the app. In most cases it completes normally. Where it does not, the usual cause is that the sign-in window and the main window are treated as different contexts, and the fix is to sign in once with the ordinary email and password route rather than the provider button. It is worth performing the sign-in deliberately during setup rather than discovering it at the start of a working day.

The third is extensions. A password manager, a clipper, or an accessibility extension that is relied on daily lives in the browser, and a standalone window does not automatically carry it. This matters most for the password manager, because a site that used to autofill now does not. Some site to app tools carry browser extensions into the generated app specifically to close this gap, which is worth checking against the extensions actually in use before committing.

None of the three is difficult. They are simply invisible until the moment they are needed, which is why it pays to walk through all three during the first few minutes rather than in the middle of something urgent.

Choosing which tools deserve an icon

Not everything should become an app. The Dock has finite width and twenty icons is no easier to scan than twenty tabs. A workable rule is to promote a site only when at least two of the following are true.

It gets opened more than about ten times a day. It needs to stay open while other work happens in front of it. It sends notifications that matter within minutes rather than hours. Two different accounts need to be signed in at the same time. Or losing it by accident, because a browser window got closed, costs real time to rebuild.

By that rule, a note taking tool usually qualifies, because it stays open and gets switched to constantly. A calendar usually qualifies. Mail usually qualifies. A documentation site almost never does, because it is opened, read and closed. An internal dashboard checked once a morning does not either.

Applying the rule honestly tends to produce four to six apps rather than fifteen, and it produces a different list than the one that would result from simply installing whatever official apps happen to exist. That is the whole point of doing it deliberately. The Supported services list is a useful place to check which of the tools on the shortlist already have a preset ready.

What to change first

Install the official Notion desktop app, because it is free and the offline mode is only available there. Then look at the browser window it did not empty, pick the single site that is opened most often and never closed, and give that one a window of its own with Safari's Add to Dock. Kagemusha covers up to three apps at no cost on macOS 12 and later, which is enough to test whether the fourth and fifth are worth it before anything is paid for.