The Mac desktop app Google never shipped

There is no installer. Google's help page for getting started with Calendar says that Calendar cannot be downloaded and installed on a computer, and points at calendar.google.com in a supported browser instead. Everything that follows is a way of making that account behave like an installed application on macOS, and each way needs a different set of steps and a different set of settings.

What makes this worth writing down carefully is that most of the setups half-work by default. Events appear, so the job looks done, and then a shared calendar turns out to be missing three weeks later, or an alert does not fire because the thing that was supposed to fire it was never running. The verification steps at the end are the part that separates a working install from one that will fail quietly.

Decide what installed has to mean before starting

Three different outcomes get described with the same word, and they need different setups.

The first is a dedicated window with its own icon, so the calendar stops living in a browser tab. The second is events that the whole Mac can see, meaning Spotlight finds them, the menu bar can show them, and other applications can read them. The third is full access to Google's own features, including appointment schedules, working hours, event email notifications and room booking on a Workspace account.

No single setup delivers all three. A web app gives the icon and every Google feature but stays sealed off from the rest of the Mac. An account added to macOS gives system-wide events and system-scheduled alerts, but three Google features stop working. A third-party calendar gives desktop behaviour and its own entry methods, with Workspace-specific tools left in the browser.

Picking the wrong one wastes an afternoon. Picking two on purpose is often the right answer, as long as the same calendar does not arrive twice, which is what creates duplicate events on the grid.

Setup one: install the web page as an application

This takes about a minute and requires nothing beyond what is already on the Mac.

In Safari, Apple documents the feature as requiring macOS Sonoma 14 or later. Open calendar.google.com, sign in, then choose File and Add to Dock from the menu bar, or use the Share button and choose Add to Dock. Give it a name and click Add. The web app is saved into the Applications folder inside the home folder, and it opens from the Dock or Spotlight like any other application.

In Chrome, open the same page, then use the More menu, the Cast, save, and share submenu, and Install page as app. Chrome's own help notes that installed web apps can get more storage for offline use, notifications, file system access and icon badges.

Three settings are worth changing immediately afterwards.

Open the web app, click its name in the menu bar and choose Settings. The application name, its URL and its icon can all be changed there, along with whether navigation controls appear in the toolbar. Removing the back and forward buttons makes it feel considerably less like a browser.

Next, add it as a login item so it opens at sign-in. Apple notes that a web app can be added as a login item like any other application, and that for sites sending notifications the Dock icon can show an unread count.

Last, turn on offline access inside Google Calendar's own settings. This is stored per browser on that machine, so enabling it in Chrome does nothing for a Safari web app and the reverse is also true.

Setup two: add the Google account to macOS

This is the setup that puts events into the system calendar database, where every other application can reach them.

Google's instructions are short. Open Apple Calendar, open its settings from the Calendar menu, go to the Accounts tab, click the Add button, choose Google, and complete the sign-in on screen. The same result comes from System Settings under Internet Accounts, and either entry point produces the same account.

Then change two things on that Accounts tab before closing it.

The Refresh Calendars setting decides how often the Mac and Google exchange changes. Google points at this control directly in its instructions. Leaving it at a long interval is the most common reason a calendar feels permanently out of date, and the most common reason people conclude the setup failed.

The calendars actually being synced are controlled on Google's side, not on the Mac. Calendars under My Calendars sync automatically, along with birthdays. Anything else, including calendars shared by colleagues and subscribed public calendars, has to be ticked on a separate calendar sync page in Google's settings and saved there. Nothing in Apple Calendar can reveal a calendar that page has not released.

Three Google features stop at this boundary

Google lists them explicitly: email notifications for events, creating new Google calendars, and Room Scheduler. Standard alerts still work, because macOS schedules those itself. A new calendar has to be created in the browser first and will then appear on the Mac once it is selected for sync.

Setup three: install a Mac calendar application

The third setup is an application built for macOS that signs into the Google account itself. Installation is the usual drag to Applications or an App Store install, and the meaningful part is the first launch.

Expect a Google sign-in window from the application, showing Google's real sign-in page and a consent screen listing what the application is asking for. An application that asks for the Google password in its own text fields rather than opening Google's sign-in is not following the standard pattern and should be closed.

Multiple accounts are worth adding on day one rather than later. A personal account and a work account added together will surface conflicts between them immediately, which is the entire reason for having both in one window. Most desktop calendars also let colour and visibility be set per calendar at this point, and doing it during setup takes a tenth of the time it takes after three months of accumulated events.

This setup coexists with setup two without any problem, as long as the same calendar is not also flowing through the system account. Two paths to the same calendar is what produces every event twice.

Where each setup keeps its copy

None of the three setups hold the calendar. Google does. What each one keeps locally is a copy, and the differences show up on the days that matter: on a flight, after a crash, and on the first morning with a new machine.

A web app keeps its copy inside the browser profile that created it. That is why offline access has to be enabled per browser, and why the copy disappears when browser data is cleared. Nothing is lost from the account, but the offline view has to be rebuilt by opening the calendar online again.

An account added to macOS is held in the system calendar database in the user library, which is what makes the events visible to Spotlight, to the menu bar and to other applications. It is included in a Time Machine backup of the home folder, and it is rebuilt automatically on a new Mac as soon as the same account is added.

A third-party calendar keeps its own cache, usually inside the application support folder, and often holds preferences that are not stored anywhere else: colours, calendar sets, default alert times, per-calendar visibility. This is the one setup where configuration can genuinely be lost, because the account holds the events but not the arrangement.

The practical consequence is small but worth knowing. Moving to a new Mac restores the schedule in all three setups by signing in again. What does not come back automatically is the arrangement built on top of it. Anyone who has spent an hour assigning colours to fourteen calendars should check whether the application syncs its settings through an account of its own before assuming they travel.

Verify the install rather than assuming it

Five checks, in order. They take about ten minutes and catch nearly everything that fails silently.

Create a test event on the Mac and confirm it appears in the browser. This proves the connection runs in both directions, not just inbound.

Count the calendars. Open the browser view, list every calendar visible there, and confirm each one that matters appears on the Mac. This is where missing shared calendars surface.

Quit the application entirely and wait for an alert on a test event five minutes out. If the alert arrives with everything closed, macOS is scheduling it. If it does not, the alert depends on something being open, which is the expected behaviour for a browser tab and worth knowing before it matters.

Edit one occurrence of a recurring event and check both views agree about whether the change applied to one occurrence or the whole series. Disagreement here is rare but expensive.

Create an event in a different time zone and confirm the displayed time matches on both sides. Time zone handling differs between calendar applications and is easier to check deliberately than to debug after a missed call.

When it does not work

Duplicate events almost always mean the same calendar is arriving by two routes at once. Remove one of them rather than hiding calendars, because hiding leaves the duplicates in search results and in other applications.

A calendar missing on the Mac but present in the browser is the sync selection page, not a bug in the application. Tick it there and save.

A calendar that syncs but refuses to update points at either the refresh interval or, in one specific case, the delegation feature. Google notes that anyone who previously used the delegation tool in Apple Calendar has to switch it off before calendar sync will work, by unchecking every calendar under Accounts and then Delegation.

Alerts that stop arriving after the Mac has been asleep for a long period are usually a sign that the calendar was never fully woken rather than a sync failure. Opening the calendar and letting a refresh complete before relying on the day's alerts is a reasonable habit on a machine that sleeps for days at a time.

On a work account, a Workspace administrator can restrict what leaves the browser. If the secret address for a calendar cannot be found under Integrate calendar, Google's help attributes that to changed sharing settings on the administrator's side. That is a question for the administrator rather than something to keep retrying.

What to change first

Start with the account in Apple Calendar so the rest of the Mac can see the schedule, set Refresh Calendars to something short, and then walk the five verification checks before trusting it with anything important. If the result is that everything syncs correctly and the week still does not fit, the problem is no longer installation, and the next thing to examine is how quickly events can be entered and whether travel time between them is being counted. Caltimate is built around those two.