A FreshBooks desktop app: invoices in a window of their own

Searching for a FreshBooks desktop app usually happens at a specific moment. An invoice is half written, a browser window with fourteen tabs in it gets closed, and the work is gone. Or a client calls, the number they are asking about is three tabs deep, and finding it takes longer than answering the question. The search is not really about features. It is about wanting accounting work to live somewhere that does not disappear when a browser does. The honest answer to the search is that no official desktop application exists, and that the gap can still be closed.

What FreshBooks actually publishes

The App Store is the fastest way to see the shape of the product. The listing is FreshBooks Invoicing App, published by 2ndSite Inc, free to install, and it requires iOS 18.0 or later. A second listing, Invoice Creator by FreshBooks, requires iOS 14.0 or later and covers a narrower job.

What matters on those listings is the compatibility block. It names iPhone and iPad. It does not name macOS. On Apple silicon a developer can choose to make an iPad app available on the desktop, and when that happens the listing says so explicitly by naming macOS and a chip requirement. Neither FreshBooks listing does, so installing the tablet build on a Mac is not an available route.

There is also no entry in the Mac App Store, and the company's own pages point to the browser and to the phone apps rather than to an installer. That is a deliberate shape, not an oversight. Accounting data has to be current across a laptop, a phone, an accountant's login and a client portal at the same time, and a browser-first product keeps a single source of truth without shipping and updating four native builds.

The practical consequence is narrow but real. Everything the product does is reachable on a Mac. None of it is reachable outside a browser. Every complaint that starts with a lost tab or a closed window comes from that single fact, and none of it comes from the software being incomplete.

Why download pages keep appearing anyway

Search results for this term include pages titled as downloads for PC and Mac. They fall into three groups, and telling them apart saves time.

The first group is emulator instructions. These pages explain how to install an Android emulator, then install the Android build of the app inside it. The result runs, and it is a phone interface at desktop size with an extra layer of software underneath. For a tool used every day to send money requests, that is a lot of surface area for a cosmetic gain.

The second group is directory sites. Several catalogues list the product under a heading like desktop app because they package a browser window themselves. What is being offered there is a wrapper, not something the accounting company built or supports. That is worth knowing before a login goes into it.

The third group is community code. A search on GitHub for a FreshBooks desktop wrapper returns projects built by individuals. Some work well. The question to ask about any of them is who keeps it running when Chrome ships an update, because browser updates are frequent and a wrapper that is not maintained tends to break quietly.

None of these three is wrong to use. The point is that all of them are versions of the same idea, which is to put the web product in a window that behaves like an application. Doing that deliberately, with something maintained, is cheaper than doing it by accident.

What a browser tab costs an invoicing workflow

A tab is a fine container for reading. It is a poor container for a task that holds state.

Invoicing holds state constantly. A draft with four line items on it, a time entry mid edit, a client record open next to the invoice being built from it. All of that lives in a tab that sits beside a research tab, a webmail tab and whatever was opened to check a supplier's address. Closing the window closes all of it. Quitting the browser at the end of a session quits the invoice too.

Then there is the problem of getting back. Command+Tab lands on a browser, not on the accounting product. The window that comes forward may be the wrong one of three, and the right tab has to be found by favicon. For something opened twenty times a day, that is a real tax.

Sign in behaviour adds to it. Accounting products expire sessions on a schedule, which is correct given what they hold. A browser used for everything else collects cookie clearing, privacy extensions and profile switches that shorten those sessions further. The result is a login prompt at the exact moment a number was needed.

The last cost is attention. A billing session and a browsing session are different modes of work. Putting them in the same window means every glance at an invoice is also a glance at everything else that was open.

What a dedicated window changes

A standalone window fixes a specific list of things, and it is worth being precise about which.

Behaviour	Browser tab	Standalone window
Survives quitting the research browser	No	Yes
Appears in Command+Tab by name	No	Yes
Own icon in the Dock	No	Yes
Cookies separate from general browsing	Shared with the profile	Isolated per app
Reopens at the invoicing screen	New tab page	The address it was built from
Closed by accident with other tabs	Often	Rarely

Session isolation is the one that pays off most. Apple documents the behaviour plainly for web apps made in Safari.

A web app functions independently of Safari. It shares no browsing history, cookies, website data, or settings with Safari. In this way, it keeps your browsing separate, similar to using a Safari profile. Source: support.apple.com

For a bookkeeping account that is read by more than one person, that isolation has a second use. A business login can sit in one window and a personal login in another, with no profile switching and no signing out to swap.

What a window does not change is the data. It is the same account, the same records and the same sync as the phone app. Nothing is stored locally that was not stored locally before, and there is no offline mode created by putting a web page in a frame.

Two free routes on a Mac, and where each stops

Safari has the feature built in from macOS Sonoma 14 onward. Open the login page, choose File then Add to Dock from the menu bar, name it, and confirm. The result is saved to the Applications folder inside the home folder and opens from the Dock or from Spotlight. Cost is zero and setup takes under a minute.

Chrome has an equivalent. Open the page, then use the menu at the top right, choose the cast, save and share group, and pick the option to install the page as an app. Google's help describes the result as accessible from the launcher or home screen, with some apps gaining notifications and icon badges.

Both routes work. Both have the same limitation, which is that the app is tied to the browser it was made in and to the profile that browser is signed into. For anyone who runs an ad blocker, a password manager and a translation extension, the Safari route restricts which extensions come along, and the Chrome route brings the whole profile with it including its other logins.

That is the point where a purpose built tool earns its place. Choosing the engine, deciding which extensions load in which window, and getting an isolated profile per app are the differences worth paying attention to, and the Features page lays out which of those are configurable. For anyone wanting to see whether the exact service is already covered before setting anything up, the Supported services list is the faster check.

Which screens deserve a window, and which do not

Not every page in an accounting product is worth separating. The test is whether the page is opened many times a day and whether losing it mid task costs anything.

Three screens usually pass that test. The invoice list is the first, because it is the page returned to after every client email and every payment notification. The timer is the second, and it is the strongest case of all, since a timer that is not visible is a timer that gets forgotten and the billing hour is simply lost. Expense capture is the third, because receipts arrive at random moments and the cost of a receipt is losing it rather than mistyping it.

Three others usually fail the test. Reports are read at month end and then closed, so a bookmark serves better than an icon. Account settings are visited a handful of times a year. The client portal view is a check of what someone else sees, which is a job for a private window rather than a permanent one.

There is a middle case worth calling out, which is a window holding several related screens at once. A single application that opens the invoice list, the timer and the expense screen as tabs on launch behaves like a purpose built billing tool, while remaining the same web product underneath. Setting that up is a matter of listing the addresses to open at start, and the Guide walks through the order those steps happen in.

What the plan decides, and what the window does not

Prices are worth stating before any of this is built, because a window changes none of them. FreshBooks lists Lite at $23 per month, Plus at $43 per month and Premium at $70 per month, with a Select tier quoted on request. Lite covers invoicing to 5 clients, Plus to 50 clients, and Premium to an unlimited number. Add-ons are priced separately: team members at $11 per month per user, advanced payments at $20 per month, and payroll at $40 per month plus $6 per month per user. A 30-day money back guarantee is stated on the pricing page.

Two implications follow. First, client limits are account limits, not window limits. Building three windows does not raise a cap. Second, a second window signed into a second business is still a second subscription, because the entitlement follows the account.

Where the window does help on cost is time. Anyone billing by the hour and opening the timer twenty times a day is spending minutes on navigation that produce nothing. Cutting that to one click has a value that is easy to calculate against whatever the plan costs.

What to change first

Pick the one screen opened most often, which for most people is either the invoice list or the timer, and give that screen a window of its own today using Safari or Chrome. Live with it for a week before building anything else, because the second and third windows only become obvious once the first one stops being a tab. When the browser engine, the extension set or a clean profile per window starts to matter, Kagemusha is where those choices are made.