Coherence X on a Mac: how it builds apps from sites

Coherence X turns up in search results next to two routes that are already installed and cost nothing, which makes the price the first thing anyone looks at. That is the wrong place to start. The useful question is what Coherence X actually builds on a Mac, how much of it is borrowed from a browser that is already there, and which of those differences still matter after the novelty of a new Dock icon wears off.

It does not ship an engine of its own

The single fact that explains most of the behaviour is that Coherence X does not contain a browser. Every app it creates runs on a Chromium based browser that is already installed on the Mac. The product page lists Chrome, Brave, Edge and Chromium including the ungoogled build as supported engines, and states that each created app runs on its own isolated browser engine. The requirement is macOS 13.5 or later, on both Apple Silicon and Intel machines. The current line is Coherence X5, which the developer describes as redesigned for macOS 26.

Borrowing the engine has consequences in both directions, and they are worth separating before anything else.

On the useful side, rendering is identical to the browser the app was built on. A payroll portal, a bank console or an internal admin screen that was only ever tested against Chrome behaves in the app exactly as it behaves in Chrome, because it is Chrome underneath. Extensions from the Chrome Web Store install into an individual app, so a password manager or an ad blocker can live inside one app without being present in the others.

On the cost side, the app is only as stable as the engine it points at. Removing or relocating the browser that an app was built on is not a cosmetic change. Version X5 addressed the maintenance half of this by shipping automatic updates for created apps, which removed the manual rebuilding step that earlier versions required after browser updates. That single change is the difference between a set of apps that quietly keeps working and a set that needs attention every few months.

What the setup actually involves

The creation step asks for four things, and each one is worth a moment of thought rather than a default.

The address is the one that is hardest to change later. Point an app at the deep link that should open every morning, not at the marketing home page of the service. A support console app that opens on the open ticket queue saves two clicks per launch, every launch. A mail app that opens on the inbox rather than the product site saves the same.

The engine comes next. Building on the browser that is already the daily driver keeps sign in sessions and rendering predictable, and building on a second browser is a deliberate way to keep an app's identity separate from everyday browsing.

Then the mode, covered below, and then the icon. Icons matter more here than they look on a specification sheet, because the whole purpose of the exercise is recognising a target in the Dock at a glance. Two apps built from the same service with the same favicon defeat the point, so a personal account and a work account want visibly different icons.

Created apps are collected in an app library where names, icons, tabs and addresses can be edited afterwards. On the two and five Mac licences, apps can be exported to other licensed users, which turns a carefully configured internal tool into something a colleague installs rather than rebuilds. For a team standardising on the same handful of admin consoles, that export path is often worth more than any individual feature.

The extension that sits inside every app

The part of Coherence X that does the actual work of making a Chromium window feel like a Mac application is a browser extension, included in every app by default.

Coherence apps are based on third-party browsers, so the Coherence extension enables additional functionality that would not otherwise be possible. The extension is lightweight, offline, and private. Source: help.bzgapps.com

Three of its jobs are the ones that show up in daily use.

Intelligent whitelisting

Most of the extension's interface is given over to rules that decide which addresses stay inside the app. Links that do not match the rules are handed to the default browser instead of opening in the app window. This is the feature that keeps a Slack app from turning into a general purpose browser the first time somebody posts a news article, and it is the single biggest behavioural gap between a wrapped app and a pinned tab.

Dock behaviour and session recall

Without the extension, closing the window of an app built on Chrome and then clicking the Dock icon produces a generic new browser window. With it, the app reopens or restores the last window the way a native application does. The developer calls this Quick Resume, and the extension also distinguishes windows the user opened from popups the engine raised, which is what stops sign in dialogs from being treated as new app windows.

The Google sign in detour

Google blocks sign in attempts from browser frames it does not recognise. The extension works around this by switching the user agent to Firefox when a Google sign in occurs, and the setting can be turned off again once the account is authenticated. Anyone who has hit a blank "this browser or app may not be secure" page in a hand rolled wrapper will recognise the problem this solves.

The extension can be disabled. In Coherence Preferences there is an option called "Automatically include Coherence extension", and deselecting it stops the extension from being added to new apps. Turning it off also removes whitelisting, session recall and the sign in workaround, which is most of the reason to use the product in the first place.

Three app modes, and what each one remembers

Coherence X asks for a mode when an app is created, and the choice determines what happens between launches.

Standard apps always open to the preset address. Pressing Command T still opens a tab, but the next launch returns to the original URL rather than to wherever the session ended. This suits a single purpose screen: a dashboard, a chat client, a ticket queue.

Tabbed apps restore their previous state instead. Closing one tab and opening another before quitting means the app comes back with both changes intact. This suits research surfaces and documentation sets where the open tabs are themselves the working state.

Incognito apps run a private session that keeps nothing. This is the mode for a second account that should not persist, or for a client environment that should leave no trace between sessions.

The mode is per app, not per licence, so a Mac can carry all three at once. In practice most people end up with a majority of standard apps and one or two tabbed ones.

What a licence covers

Pricing is per Mac, not per app.

Licence	Price	Activations
1 Mac	39.99 USD	One Mac
2 Macs	59.99 USD	Two Macs
5 Macs	99.99 USD	Five Macs

Every tier allows an unlimited number of created apps and includes bug fixes, minor updates and support. The two and five Mac tiers add the ability to export apps to other licensed users, which matters for a team standardising on the same set of internal tools. A 14 day trial is available before buying, and enterprise and custom licences are offered on request.

The upgrade terms are the part worth reading twice. A Coherence X5 licence covers all 5.x releases. A future major version is a new purchase, with a discount for existing owners, and holders of a 4.x licence are offered up to 25 percent off the move to X5. This is a buy once model with paid major upgrades, not a perpetual licence for the product name.

How it lines up against the routes that cost nothing

	Safari, Add to Dock	Chrome, install as app	Coherence X
Requirement	macOS Sonoma 14 or later	Any current Chrome	macOS 13.5 or later, plus a Chromium browser
Engine	System WebKit	Chromium	The installed browser it was built on
Session	Isolated from Safari	Shared with the Chrome profile	Isolated per app
Two accounts, one service	Yes	No, it follows the profile	Yes
Custom icon	Yes, in the app's settings	No, taken from the site	Yes
Extensions	Safari extensions, per app	Chrome extensions from the profile	Chrome Web Store, per app
Links to other sites	Open in the app	Open in the app	Rules decide, the rest go to the default browser
Dock click after closing	Reopens the app	Generic browser window	Restores the last window
Cost	Free	Free	From 39.99 USD, 14 day trial

Read the table as three answers to the same question rather than a ranking. For two or three sites that only need their own window and their own login, the built in routes already do the job and cost nothing. The paid route earns its price where link handling, per app extensions, custom icons and repeatable setup across several Macs all apply at once.

Which sites are actually worth an app

The failure mode with any of these tools is enthusiasm. Twenty wrapped apps in the Dock reproduce the problem that thirty tabs created, with worse search. Three questions filter the list.

Is it opened every working day, without exception? Weekly is not enough. An icon that is not the target still costs a glance every time the Dock is scanned.

Does it need to reach the reader without the browser running? Notifications that must not be missed, a window that should survive a browser restart, a screen that should be one keystroke away when everything else is buried.

Does it need an identity separate from the browser? A second account on the same service, a client environment that must not touch personal logins, an admin console that should never sit next to the public site. A pinned tab can do almost everything except this.

Sites that clear all three usually number between three and six. Checking a Supported services list before configuring anything by hand is faster than starting from a blank URL field, and a Features page is where to confirm whether a given tool covers icons, isolated sessions and link rules rather than merely opening a window. The Pricing page is worth reading against what the free routes already deliver, because for a short list they frequently deliver enough.

What to change first

Take the one site that gets opened before anything else each morning and give it a window of its own, using whichever route is already installed. Live with it for a week and watch whether the tab hunting actually stops. If it does, Kagemusha and the paid tools are worth pricing against the time saved, and if it does not, the problem was never the browser.