Harvest desktop app on a Mac: logging hours without a tab

Looking for a Harvest desktop app usually means one of two things, and they pull in different directions. Either the timer needs to be one keystroke away instead of buried in a browser tab, or the reports and invoices need a window that does not vanish when the browser is closed with everything else. Harvest ships an official Mac app that answers the first need. It does not answer the second, and that gap is where most of the wasted time in this decision goes.

What Harvest ships for the Mac today

Harvest's apps page lists mobile apps for iPhone and Android and desktop apps for Mac and Windows. The Mac app is a real download, and it is the intended way to start and stop the timer without opening a browser at all.

The free plan matters here, because the app is not gated behind a paid tier. Harvest's pricing page lists a Free plan at $0 forever with one seat and two projects, and the features named in that plan include time tracking, invoicing, expense tracking, and Mac and iOS apps. A freelancer tracking two projects can therefore run the official Mac timer without paying anything.

The paid tiers are priced per seat. Teams starts at $9 per seat per month when billed annually, which the page states as $108 per seat billed annually, or $11 per seat per month billed monthly. Enterprise starts at $14 per seat per month annually, listed as $168 per seat annually, or $17.50 per seat monthly. Enterprise Plus is custom priced. Paying for a year up front applies a 20 percent discount, and the trial runs 30 days with no credit card collected.

One detail from the site is worth noting for anyone deciding how much to build on top of Harvest: the footer now carries Bending Spoons Operations S.p.A. as the copyright holder.

What the Mac app covers and what it does not

The desktop app is a timer. That is its job, and for tracking hours it is the right tool: it starts, it stops, it survives a browser being closed, and it does not need a tab.

Everything else Harvest does happens on the web. Invoices are created and sent there. Reports and analysis are read there. Expense receipts are attached there. Client and project setup, team capacity, budgets, and approvals are all web pages. So is Harvest Forecast, the scheduling product that appears under Harvest's own features menu and has its own sign in.

That split produces a familiar pattern. The timer becomes an app, which solves the ten times a day problem. The invoicing and reporting side stays in a browser tab, which is the once a week problem, and once a week is exactly the frequency at which a tab gets lost, closed, or signed out.

The honest division is that the official app handles the timer and a separate window handles the rest of Harvest. Both halves get used. Only one of them currently has somewhere to live.

There is a second case where the browser side is the whole job. Anyone who runs a studio but does not personally track hours, an office manager who invoices and chases payment, or an accountant who pulls reports at month end, has no use for a timer at all. For them the Mac app is beside the point and the web interface is the product.

Why the invoicing side keeps getting lost

A browser tab is a poor home for anything that is important but infrequent. Three things go wrong repeatedly.

Sessions collide. Anyone who works with two Harvest accounts, for example a contractor inside a client's account plus a personal one, cannot keep both signed in within one browser profile, because cookies are shared. The workarounds are a second browser, a private window that has to be signed into every time, or signing out and back in.

Windows get closed. Quitting a browser at the end of the day takes the half written invoice with it. The web app remembers a draft, but the habit of reopening the tab and finding the right page again is friction paid daily.

Attention gets taken. Invoicing is careful work: amounts, rates, and a client's name. Doing it in the same window as research tabs, a video, and a mail client is how the wrong hourly rate reaches a client.

None of that is a criticism of Harvest. It is the cost of a web interface having no window of its own, and the fix is a window rather than a different service.

The web side carries the money, not just the pages

There is a reason to treat the browser half as more than a convenience. Harvest's paid plans are built so the base rate covers core features while additional invoices, projects, clients, and tasks are billed according to use. That wording appears on the pricing page under both the Teams and Enterprise plans. Whatever else that means for a given account, it means the invoicing screens are where the bill is shaped, and those screens are web pages.

The accounting handoff sits on the same side. The Teams plan lists accounting and payment integrations, naming Stripe, QuickBooks Online, Xero, and Deel among them, and Harvest's integrations pages add Asana and Slack to the picture. Connecting or reauthorising any of those happens in the browser, and reauthorisation is precisely the kind of task that arrives unannounced when a token expires.

Enterprise adds features that are administrative rather than clerical: unlimited custom reports, profitability reporting by client, project, task, and team, timesheet approvals, an activity log of time entries and changes, SAML based single sign on, and a setting that requires notes on every time entry. Every one of those is read or configured on the web. A team paying for that tier is paying mostly for pages the timer never shows.

Putting the web side in its own window

A tool that turns a website into a standalone Mac app produces an actual application from a URL. It has a Dock icon, a name in the Command Tab switcher, and a window that closing a browser cannot take down. The page inside is the same Harvest interface, kept current by Harvest, so there is no separate build to update or feature to wait for.

Three properties decide whether this sticks in practice.

Each generated app carries its own browser profile, so cookies and sessions are isolated. Two Harvest accounts, or a Harvest account and a Forecast account signed in with different identities, stay signed in at the same time. That is the single most common reason people keep a second browser installed, and it stops being necessary.

Chrome Web Store extensions keep working, because the app runs on a Chromium engine. A password manager fills the Harvest login exactly as it does in the browser. That matters more than it sounds: a window where signing in is awkward is a window that gets abandoned within a fortnight.

A quick setup step can open more than one URL as tabs on launch, which suits this case well. Harvest reports plus Harvest invoices, or Harvest plus Forecast, opening together in one window means the month end routine is one icon instead of four bookmarks. The features list covers the per app profile and the tab controls in detail.

The routes side by side

Route	Start and stop the timer	Invoices and reports	Survives closing the browser	Own Dock icon	Two accounts signed in at once
Harvest Mac app	Yes	No	Yes	Yes	No
Harvest in a browser tab	Yes	Yes	No	No	No
Page installed from Chrome	Yes	Yes	Yes	Yes	Shares the Chrome profile
Harvest in a standalone web app	Yes	Yes	Yes	Yes	Yes, one profile per app

The third row deserves a note, because it is free and already on the machine. Chrome 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 windowed app with its own icon. What it does not get is a profile of its own: the installed page runs inside the profile it was installed from, which is why the uninstall dialog offers to also delete the data from Chrome. For one Harvest account that is enough. For two, it is the same collision as a tab.

What to check before changing anything

How many hours a day does the timer actually get started? If the answer is many, the official Mac app earns its place regardless of what happens to the rest.

How many Harvest accounts, and whose? One account is a simple case. A contractor with a seat in two client accounts is the case that breaks a single browser profile.

Is Forecast in use? It is a separate product with a separate sign in, reached in a browser, so it is a second page needing a home rather than something the Harvest timer covers.

Who else uses this Mac? On a shared machine, an invoicing interface left signed in inside the general browser is one click away for whoever sits down next.

What happens at month end? If invoicing and reporting is a fixed routine, it is worth one window that opens exactly the pages that routine needs, rather than a hunt through bookmarks each time.

Is the team growing this year? Seat counts change what the browser side is used for. On a single seat it is invoicing. Past a handful of seats it becomes approvals, capacity, and budget alerts, which are checked daily rather than monthly, and daily checking is the threshold where a dedicated window stops being a nicety.

What actually improves

The gain is not in how Harvest works. Harvest works the same in every window. The gain is in where it sits.

A timer with a Dock icon gets started, because starting it costs one keystroke. Hours that get logged as they happen are hours that get billed, which is the whole point of the product.

An invoicing window that is separate from browsing is a window where the wrong number is less likely to be typed, and where a half finished invoice is still there tomorrow. Two accounts that stay signed in stop turning a five minute check into a sign in cycle.

And the setup survives a change of machine, because a standalone web app is built from a URL rather than downloaded and approved. The guide covers making the first one, and the supported services list shows which sites come preconfigured.

What to change first

Install the official Mac app if the timer is the thing being started all day, since that is exactly what it is for. Then give the invoicing and reporting side a window of its own so it stops being a tab: Kagemusha is free for up to three apps, enough to test Harvest and one more daily page before spending anything.