Mac invoicing apps: native app or browser tab?

Search for a Mac invoicing app and most of what comes back is a website. Some of it is a website in a wrapper, with a Dock icon and its own window, which is closer but not the same thing. A few are actual Mac apps.

The distinction sounds like something only a developer would care about. It is not. It changes what you can do on a bad connection, whether your records show up when you search your Mac, how fast the thing feels at four in the afternoon, and who ends up holding your client list. Sometimes it changes those things in favour of the website. Here is how to tell which situation you are in.

What can a native Mac app do that a browser tab cannot?

Show up when you search your Mac. Spotlight indexes what native apps give it. That means a client’s name typed into Spotlight can surface the invoice itself, not just the app that contains it. A web app cannot do this at all, because its data is not on your machine to be indexed. Whether a given Mac app does it is up to that app, but only a Mac app can.

Keep working when the connection does not. More on this below, because it deserves its own section and the honest answer is more interesting than the obvious one.

Use the whole keyboard. Native apps get the standard Mac menu system, which means every command has a discoverable place and a shortcut, and the ones you use constantly become muscle memory. Browsers already own many of the useful key combinations, so web apps work around them, and the workarounds are rarely consistent between one app and the next.

Tell you something without being open. A Dock icon can carry a badge. Ledger puts your outstanding revenue there, so the number is visible when the app is closed and you are doing something else entirely. That is a small thing that a browser tab structurally cannot do: a closed tab is nothing at all.

Reach the rest of your devices properly. A Mac app built on Apple’s frameworks can extend to iPhone, iPad, Apple Watch and Vision Pro as the same app rather than as a separate mobile product, and it can put a glance sized view on a watch face or a dashboard on an Apple TV. A web app can be responsive, which is not the same as being at home on the device.

Behave like everything else on your Mac. Printing, PDF export, Quick Look, the share sheet, drag and drop between apps, Dark Mode, and text that respects your accessibility settings. Native apps get these because the system provides them. Web apps reimplement each one, or do without.

Does an invoicing app really need to work offline?

Here is where the usual argument overreaches. You almost always have a connection, and four paragraphs about being stuck on a plane would not be honest, because you are rarely on a plane.

The realistic version is smaller and more common. Hotel wifi that resolves DNS but stalls on uploads. A client’s guest network with a captive portal that logs you out every twenty minutes. A site visit in a basement. Your provider having a bad afternoon. In every one of those, the question is not whether you can browse the web. It is whether a half working connection loses the invoice you were part way through writing.

A native app answers that by keeping your data locally and syncing when it can. The work is on your machine either way, so a flaky connection is an inconvenience rather than an interruption. A web app answers it with drafts and caching, which mostly works, and occasionally does not, and you find out which at the worst moment.

There is a related benefit that has nothing to do with outages. Local data is fast. Searching, filtering and totalling happen at the speed of your Mac rather than the speed of a round trip to a server. It stops mattering when your records are small and starts mattering a lot when they are not.

Do you need an account to send an invoice?

A web app has to know who you are before it can show you anything, so an account is not a business decision, it is architecture. Once the account exists, your invoices and your client list live on someone else’s servers, because that is where the app runs.

A native app does not need any of that. Ledger has no account at all. Your records sit on your device, and if you want them on your other devices they go through your own iCloud account, which you already have and already control. You can also switch sync off and keep everything on one Mac.

This is worth thinking about specifically because of what invoicing data is. It is your full client list, what you charge each of them, and what they still owe. That is a fairly complete picture of your business, and it is exactly the sort of thing worth knowing the location of.

Where does the browser have the advantage?

Two things, stated plainly, because they are the two that decide it for some people.

More than one person in the books. A web app hands out logins. An app that keeps its records on your own devices is built around you and your devices, and shared access is what it does least well.

More than one kind of device. If a Windows desktop or an Android phone is part of your working week, a browser is the only thing all of them agree on.

Neither is about the invoice itself. They are about who else is in the file and what they are running.

How can you tell which one you are looking at?

Marketing pages rarely say, and a wrapped website looks like an app until you use it. Four tests, none of which take longer than a minute:

Turn the wifi off and open it. A native app shows you your records. A wrapped site shows you a blank window or an error.

Look at the menu bar. A real Mac app has File, Edit and its own menus with shortcuts beside the commands. A wrapper has a menu bar with almost nothing in it.

Try to open it without signing in. If it insists on an account before showing you anything, its records are on a server rather than your machine.

Search for a client in Spotlight. If the records are on your Mac and the app indexes them, they come up. If nothing does, they are not on your Mac.

So which should you choose?

Start with what you are running. If the devices you work on are Apple ones, a native app is not a different flavour of the same thing: it indexes into Spotlight, works on a bad connection, keeps the whole keyboard, and reaches a watch face and a television as the same app rather than a separate product.

Then ask who else needs to be in the file. If other people work in your books every week, that is the one axis where the browser is straightforwardly ahead, and it will outweigh the rest.

For a business that runs on Apple devices and keeps its own books, Ledger is built the way this article describes. A Mac app first, extending to iPhone, iPad, Apple Watch, Apple TV and Vision Pro, with your records on your own devices, no account to create, and one payment rather than a monthly fee.

The point of knowing the difference is that “invoicing app for Mac” describes two quite different products, and it is worth knowing which one you are signing up for before the trial ends.