HoneyBook desktop app on a Mac: client work in one window

Searching for a HoneyBook desktop app ends the same way for everyone: there is nothing to download. HoneyBook publishes apps for iPhone and Android, and on a computer it is a web application. That is not a gap in the product so much as a decision about where it lives, and it leaves one real question for anyone running client work from a Mac. Invoices, contracts, and proposals are being written in the same window as research tabs, a mail client, and whatever autoplayed at the wrong moment. There are three ways to change that, and they are not equally good.

What HoneyBook actually ships

The mobile apps are linked directly from HoneyBook's own site: an iPhone app on the App Store and an Android app on Google Play. For the desktop there is no installer, no disk image, and no Mac build. The product is reached in a browser at HoneyBook's web application, and that web application is the full product rather than a cut down version of it.

Two facts from HoneyBook's own pages belong in any plan built on it. The first is geography. The location prompt shown on HoneyBook's site states that it supports professionals located in the United States, Canada, the United Kingdom, and Australia, and offers to collect an email address for anyone elsewhere. The second is the shape of the plans, because it decides how much of the interface is in daily use.

HoneyBook's pricing page lists three tiers when billed yearly. Starter at $29 per month includes unlimited clients and projects, invoices and payments, proposals and contracts, a calendar, the professional templates, a client portal, basic reports, up to two live lead forms, and HoneyBook AI. Essentials at $49 per month adds the scheduler, automations, the QuickBooks Online integration, up to two team members, up to ten live lead forms, SMS reminders, removal of the Powered by HoneyBook mark, and standard reports. Premium at $109 per month adds unlimited team members, priority support, multiple companies, advanced reports, and unlimited live lead forms. The page also shows promotional pricing against higher list figures, so the numbers on screen on any given day may be discounted.

Every one of those features is a web page. Which means the browser window is not a convenience layer over HoneyBook. It is HoneyBook.

What that window is actually being used for

It is worth being concrete, because the case for separating it rests on what happens inside it.

Money is committed there. An invoice with the wrong rate, a proposal sent to the wrong client, or a contract with the wrong date are all one mistyped field away, and all three are the kind of mistake that gets caught by the client rather than by the sender. Careful work does not belong in a window that also holds twelve tabs.

Clients see part of it. The client portal, lead forms, and scheduling links are the outward face of the business, and checking how they look is something done repeatedly while setting them up.

It runs unattended. Automations fire on triggers, and the scheduler accepts bookings whether or not anyone is watching. A session that has been signed out, or a browser that was quit, is not the problem for automations, but it is the problem for noticing what they did.

And it is connected to everything else. HoneyBook's integrations page lists Gmail and Outlook for sending from a business address, Zoom for meeting details, Calendly for availability, QuickBooks Online for accounting, Slack, Zapier for everything else, and separate connectors for ChatGPT and for Anthropic. Every one of those is authorised in a browser, and reauthorised in a browser when a token expires.

The three ways off the tab strip

The first route is a browser tab that never gets closed. It is free and it is what almost everyone does. It fails in ordinary ways: quitting the browser takes it down, a window with thirty tabs makes it hard to find, and the session is shared with everything else signed in inside that profile.

The second route is installing the page from Chrome. Google documents the step as Install page as app, under the More menu and its Cast, save, and share submenu, in the Chrome help pages. The result is a real window with its own icon in the Dock, and for a single HoneyBook account it is a genuine improvement over a tab at no cost. What it does not get is a profile of its own. The installed page runs inside the Chrome profile it was installed from, which is why the uninstall dialog offers to delete the data from Chrome as well.

The third route is a tool that turns a website into a standalone Mac app. It produces an application from a URL with its own icon, its own window, its own entry in the Command Tab switcher, and its own isolated browser profile. That last part is what the other two routes cannot do, and it is what decides the cases below.

When profile isolation is the whole point

Three situations turn session isolation from a nicety into the deciding factor.

Two businesses. Premium lists multiple companies as a plan feature, so one account can hold more than one brand. Plenty of people instead have two separate HoneyBook accounts, for example a photography business and a coaching practice, or a personal account plus a seat in a partner's. Two accounts cannot both stay signed in inside one browser profile, because they share cookies, and one signs the other out.

A shared Mac. A studio machine or a front desk computer with a signed in client management interface is one click away for whoever sits down next. A separate app with its own profile does not make that secure on its own, but it stops the session from being incidental to general browsing.

Google identities that fight. HoneyBook's Gmail integration links a sending address, and anyone with a personal Google account and a business Google account signed into the same browser knows how that ends. Separate profiles keep the right identity attached to the right window.

A generated app also keeps Chrome Web Store extensions working, because the engine is Chromium based, so a password manager fills the login the same way it did in the browser. The features list covers the per app profile and the extension support, and the tool runs on macOS 12 and later.

The routes side by side

Route	Own Dock icon	Survives quitting the browser	Isolated session	Two accounts at once	Cost
Browser tab	No	No	No	No	Free
Page installed from Chrome	Yes	Yes	Shares the Chrome profile	No	Free
Standalone web app	Yes	Yes	Yes, one profile per app	Yes	Free for up to three apps
HoneyBook mobile app	On the phone	Not applicable	Yes	One account per sign in	Included

Read it as a set of trade offs. For one account on a personal Mac, the second row is enough and costs nothing. For two accounts, a shared machine, or a setup where the Google identity matters, the third row is the only one that answers the question. The mobile app stays relevant regardless, because a phone in a pocket notices a new inquiry faster than a window on a desk.

What it costs to get this wrong

The pricing above is the useful context. A Starter plan at $29 per month billed yearly is $348 a year, and Premium at $109 per month is $1,308 a year. Against those figures, the window the product is used in costs nothing either way, which is why it is worth ten minutes rather than a debate.

The expensive failures are not licence fees. They are a proposal that sat unsent because the tab was closed, a lead form that was never checked after being changed, an automation that kept emailing a client who had already paid, and an invoice with last year's rate. Each of those is a consequence of the interface being awkward to reach and easy to lose, not of the plan being too cheap.

There is a smaller cost worth naming as well. Time spent signing out of one account and into another, several times a week, is real time. Two windows that both stay signed in removes it entirely, and the guide shows the whole setup from a URL.

Questions that settle it in five minutes

How many HoneyBook accounts are involved? One account makes this simple. Two makes profile isolation the requirement rather than a preference.

Who else uses this Mac? If the answer is anyone, the client management interface should not be a tab in the browser everyone opens.

Is the phone already carrying the notifications? If new inquiries arrive on a phone, the desktop window is for careful work rather than for alerts, which changes what it needs to be: fewer interruptions, not more.

Which integrations are live? A setup with Gmail, QuickBooks Online, and Zapier connected has three authorisations that get renewed in a browser, and renewing them in the right profile as the right identity is the difference between two minutes and an afternoon.

Does the client facing side get checked? Lead forms, the client portal, and scheduling links are all worth viewing as a client sees them, which is a second window rather than the same one signed in as the owner. A separate app with its own profile is a straightforward way to do that.

What actually improves

None of this changes how HoneyBook works. Contracts, invoices, and automations behave identically wherever the page is open. What changes is where the work sits and how easy it is to reach.

A dedicated window is reached by keystroke instead of by hunting a row of favicons, and quitting a browser at the end of the day no longer closes the business. Careful work happens in a window with nothing else in it, which is the cheapest error reduction available.

Two accounts stay signed in at once, so switching businesses is a click rather than a sign out cycle. The right Google identity stays attached to the right window. And because the page inside is the same web application HoneyBook keeps updating, nothing lags behind: there is no separate build waiting for a release. The supported services list shows which sites are already preconfigured for this.

What to change first

Put HoneyBook in its own window today, and keep the phone app for noticing new inquiries. If there is only one account and one user, Chrome's Install page as app is enough and free; if there are two accounts, a shared Mac, or a Google identity that keeps switching, use a tool that gives each app its own profile. Kagemusha is free for up to three apps, which covers HoneyBook and two more daily pages before anything is spent.