What a native Gmail app for Mac actually is

“Native” is the most-used word on every Gmail app’s page, and it means at least three different things. Here is the definition Hark holds itself to, which parts of the app are built with macOS’s own frameworks, and the one place it uses the system’s web engine — and why.

Three things “native” is used to mean

The word is doing different work on different product pages. Before deciding whether you want a native Gmail app, it is worth knowing which one is being offered.

A Dock icon

The app is the Gmail website, loaded inside a copy of a browser that ships with the app. You get an icon, a window and notifications; what is inside the window is the same web page you had in a tab. This is the loosest meaning and the most common one.

A Mac look

The interface is a web page too, but it is styled to resemble macOS — the right greys, a sidebar, a toolbar. It can look convincing in a screenshot. Under the pointer it still behaves like a page: text that selects when you meant to drag, menus that are drawn rather than the system’s, a browser engine to start before anything appears.

Built with the platform’s frameworks

The list is a real list view, the menus are the menu bar’s, the text field is the system’s text field with its spelling and dictation, the window is a window the OS knows how to tile, hide and restore. Nothing has to be started before the app can draw. This is the meaning Hark uses, and the rest of this page is what it covers.

What is native in Hark, specifically

• The whole interface. Message list, sidebar and labels, toolbar, search, Settings, the calendar grid and its editor, the Tasks panel: SwiftUI and AppKit, drawn by macOS. Light and dark follow the system or your choice, and the accent is one you pick.
• The composer. Writing a message happens in a real macOS text view — bold, italic and underline from the formatting bar, the system spell checker, the standard Edit menu, links and inline images — not in a page pretending to be one.
• The sync engine. A core written in Rust runs on your Mac, talks to Gmail, Calendar and Tasks through Google’s APIs, and keeps a local database so the inbox opens from disk rather than from the network.
• Everything the desktop provides. Notification Center, a Dock badge, a menu-bar glance at what is new, separate windows for composing, Spaces, ⌘Tab, and updates that install in place.

The one place it uses a web engine, and why

HTML mail is HTML. A newsletter, a receipt, a calendar invitation from a colleague — these arrive as web documents, and the only faithful way to show one is with a web engine. Hark renders message bodies with WebKit, the engine that is already part of macOS and the one Apple Mail uses for the same job.

That is a different thing from bundling a browser. Nothing extra ships inside the app, nothing has to boot before the interface appears, the engine is updated by macOS rather than by us, and it is used for the document in the reading pane — never for the app around it. When you reply, the original message is carried below your text exactly as it arrived, so a quoted thread survives a round trip intact.

What the difference feels like

• Opening is opening. The inbox comes from a local database, so it is on screen before the network has answered, and what has already synced stays readable when there is no network at all.
• Search is Gmail’s search. from:, has:attachment, is:unread, newer_than:7d— the operators go to Google as typed, and the results are the ones Gmail would give. A search you like can be turned into a Gmail filter, which then runs on Google’s side for every device you read mail on.
• The desktop behaves. A notification is a macOS notification, silent while Hark is the app in front. The Dock badge shows the same unread count Gmail shows. ⌘W closes the window you meant. A compose window can sit on another Space.
• One process, doing one job. There is no browser underneath sharing memory with forty other tabs, and no second copy of one carried inside the app.

What native does not mean

• Not a different Gmail. Labels, filters, the signature, the vacation responder: they are your Gmail’s, read and written through the API. Change one in Hark and the web sees it; change it on the web and Hark sees it. Snooze is the one exception — Google keeps it off the API, so Hark holds the wake-up time on your Mac and returns the conversation itself.
• Not independent of Google. Sending, and anything that changes your mailbox, needs a connection. And Google’s permissions still bound what Hark may do — a deleted message goes to Trash, for instance, because Hark deliberately does not ask for the permission that would let it delete permanently.
• Not finished. Hark is in beta. It connects one Gmail account per install, its keyboard layer is small today (j, k, the arrow keys and Esc), and a handful of Gmail settings the API does not expose are listed as links to Gmail on the web rather than left out.

If the calendar half is what you came for, there is a separate piece on Gmail and your calendar in one native Mac app, and one on how Hark is built so your mail never reaches us.

Questions