Gmail Mac mail app: native client or the web in a window

Two Gmail accounts, one browser, and a URL that ends in u/0 or u/1 depending on which one loaded first. Links from Slack open in the wrong account, the reply gets written from the wrong address, and the tab is buried behind everything else by ten in the morning. Searching for a gmail mac mail app returns answers to two different questions at once, and they are not interchangeable. One is a native mail client that connects to Gmail. The other is the Gmail interface itself, moved out of the browser and into its own window. Deciding which of those is wanted takes about a minute and saves a lot of trial installs.

The two products behind one search

A native client is a Mac application that speaks a mail protocol. It downloads messages, renders them with its own code, and presents an interface designed by whoever wrote the client. Apple Mail and Mimestream both work this way. The interface is native, the shortcuts are native, and the offline behavior is real.

A container is different. The interface stays exactly as Google built it, and what changes is the window it lives in: a separate bundle in the Dock, a session that does not collide with the browser, and no tab strip.

The dividing line is whether the Gmail interface itself is the thing being kept or the thing being escaped. Someone who has spent years learning Gmail keyboard shortcuts, filters, and search operators loses all of that in a native client. Someone who finds the Gmail interface slow and wants something that behaves like a Mac application gains exactly what a container cannot provide.

Apple Mail, the one already installed

Apple Mail costs nothing and is present on every Mac, which makes it the default answer. It connects to Gmail over IMAP, and that protocol choice explains most of what feels odd afterwards.

Gmail is not folder based. A message can carry several labels at once, and IMAP has no way to express that, so each label arrives as a separate mailbox and the same message appears in each of them. Archiving, which in Gmail means removing the inbox label, becomes a move between mailboxes. Gmail's inbox categories, the split between Primary and the rest, have no IMAP equivalent and do not appear at all.

None of that makes Apple Mail a poor client. For a single account used as ordinary mail, with folders rather than layered labels, it is a fast native application with excellent system integration and no cost. The friction shows up in proportion to how much of Gmail's own model is actually in use.

Mimestream, a native client built on the Gmail API

The alternative to IMAP is Google's own interface. Mimestream is a macOS client built on the Gmail API rather than IMAP, and its feature list follows directly from that decision: inbox categories, full label support including color coding and visibility settings, server side filters managed inside the app, and Gmail backed search rather than a local approximation of it.

The practical numbers are on the pricing page. The individual plan is $49.99 per year or $4.99 per month, with a fourteen day trial that does not ask for a card. There is no one time purchase option, which the company states directly. A licence covers all Google accounts on up to five devices and can be shared with immediate family. Distribution is direct rather than through the App Store, and the directly distributed build is sandboxed, notarized, and signed with an Apple Developer ID. It requires macOS 12 Monterey or newer.

Two smaller details are worth knowing before trialing it. Tracking prevention blocks trackers from more than 75 common services. And notification schedules can be set per account profile, so a work account can go quiet outside working hours while a personal one stays on.

Keeping the Gmail interface, changing only the window

The third answer keeps Google's interface intact and fixes the window instead. Two free routes exist.

Safari offers File, then Add to Dock, on macOS Sonoma 14 and later. The result is a real bundle in the Applications folder of the home folder, and Apple documents that it holds no browsing history, cookies, website data, or settings in common with Safari. For mail that isolation is the whole point: the mail app stays signed in to the account it was built for, regardless of what happens in the browser.

Chrome documents the equivalent as More, then Cast, save, and share, then Install page as app. It is quicker to reach, but the resulting app belongs to the Chrome profile that made it, so it shares its login with the browser.

Everything Google built survives either route. Keyboard shortcuts, filters, search operators, labels, categories, add ons from the Google Workspace Marketplace. Nothing has to be relearned, because nothing changed except the frame around it.

The account switching problem, which decides most cases

Gmail distinguishes signed in accounts by a number in the URL path. The first account signed in becomes u/0, the second u/1, and so on. The numbering depends on sign in order, not on which account is which, and it can change.

Two consequences follow. A link to a specific message opens in whichever account currently holds that number, which is how a work thread ends up open in a personal inbox. And a bookmark or a launcher entry pointing at a numbered URL is only correct until the order changes.

A container with its own browser profile removes the problem at the source. Each app holds one signed in account, so there is no numbering to get wrong. This is where the free routes differ most: a Safari web app gets its own session automatically, a Chrome installed app needs a separate Chrome profile created by hand, and tools that assign a profile per app do it as the default behavior. The supported services list covers 318 services with URL, official icon, and app name already paired, and Gmail is among them, so building the second account's app is the same three clicks as the first.

Four answers side by side

Option	Cost	Gmail labels and categories	Multiple accounts	Offline
Apple Mail	Free, preinstalled	Labels arrive as mailboxes, categories absent	Yes, in one window	Full local store
Mimestream	$49.99 per year or $4.99 per month	Full, via the Gmail API	Yes, unified or separate	Local cache
Safari Add to Dock	Free	Exactly as Gmail renders them	One app per account	Whatever Gmail offers
Browser based site to app tool	Free for three apps, 3,980 yen unlimited	Exactly as Gmail renders them	One app per account, own profile	Whatever Gmail offers

The last column is the one people forget to check. Native clients hold messages locally and open on a train. A container is the web page, so it is only as offline capable as the page is.

Extensions and add ons only survive in one direction

Anything bolted onto Gmail travels with the interface, not with the account, and this catches people out on the way to a native client.

There are two separate families. Google Workspace Marketplace add ons run inside the Gmail page itself, in the side panel next to a message. Browser extensions run in the browser around the page, which is where password managers, writing assistants, and clipping tools for note taking apps operate.

A container keeps both, because the page is unchanged and the engine is still a browser. In a Chromium based app the extensions come from the profile that app uses, which means they can be enabled per app: a password manager in the mail app, nothing else. In a Safari web app the Extensions tab in the app's own settings turns individual Safari extensions on and off for that app alone.

A native client keeps neither. Whatever the client itself implements is what exists. That can be a feature rather than a loss, since a mail window with nothing injected into it is faster and quieter, but it should be a decision rather than a surprise discovered a week in.

What a trial should actually test

Fourteen days is enough to answer this properly if the right things get tested in the first hour rather than the last.

Start with sending identity. Most long lived Gmail accounts send as more than one address, and a reply going out from the wrong one is the failure that matters most. Confirm the alias list appears and that signatures follow the address.

Then test search the way it actually gets used. Anyone who types operators such as from, has attachment, or before with a date is relying on Gmail's own search, and a client that indexes locally will not return the same results. Run three real searches from memory and compare.

Third, check the workflow that is done twenty times a day, whichever it is. Archiving with a single key, snoozing, applying a label from the keyboard, or triaging by category. Speed on the common path decides whether the client survives the month.

Finally, look at calendar invitations and large attachments, since both involve other Google services rather than mail alone. Invitation responses and Drive links are where a client that only speaks mail shows its edges.

Notifications, badges, and Focus modes

Mail is the one case where notification routing is worth setting up properly, because the whole point is knowing when something arrives without watching for it.

Apple's documentation is specific about the order of operations for a web app: the site's notification request has to be answered inside the web app rather than in Safari. Answer it in Safari first and the web app never registers. Once done correctly, the app appears in System Settings under Notifications by its own name, and the unread count shows as a red badge on the Dock icon.

The larger benefit is Focus. Notifications are routed per application, so mail in its own bundle can be allowed through during a work Focus while the browser stays silent, or silenced in the evening while everything else continues. A pinned tab cannot be separated this way, because macOS sees only the browser.

Native clients get this for free, and Mimestream goes further with per account schedules. That is a real advantage of the native route, and one worth weighing against everything that is lost by leaving Gmail's own interface.

Decide by which side of the line the requirement sits

Answer one question before installing anything: is the Gmail interface the problem, or is the browser window around it the problem. If the interface is the problem, the trial versions of a native client are the next step, and the fourteen day window is enough to find out whether the Gmail habits transfer. If the window is the problem, build a separate app per account today and let the numbered URLs stop mattering, which is what the Kagemusha pricing page describes for three apps at no cost.