Desktop App vs Web App: Why Your Calendar Belongs on Your Computer

A calendar is small, personal and needed at the exact minute a meeting starts. That makes it a poor fit for a browser tab and a good fit for an app that runs on your own computer: it keeps a copy of your schedule on the device, it doesn't share a runtime with every other website you have open, and it can sit in the menu bar instead of behind a tab.

This post is the longer version of that argument. It was prompted by a very public debate about where computer memory should live.

What Sam Altman said about RAM

On the Cheeky Pint podcast published on 29 October 2026, OpenAI CEO Sam Altman told Stripe co-founder John Collison that personal computers are an inefficient place for scarce memory. From the official transcript:

“From a global allocation perspective, actually, it's quite terrible to have everybody have a bunch of the world's limited supply of DRAM sitting in their own computer. And, being used… 5% of the time. You want maximum utilization in the cloud if you're trying to deal with this very supply constrained environment.”

Context matters here. He was talking about local AI inference, meaning running large models on your own machine, during a memory shortage driven by AI demand. He wasn't talking about calendars or everyday apps. A post with the quote on X passed 22 million views within a few days.

For expensive, shared compute, the utilization argument is fair. But it invites the reverse question for the software you open every day: which apps actually gain from running on someone else's computer, and which are better off on yours?

Why a calendar belongs on your computer

Google Calendar keeps your events on Google's servers, and that's the right place for them. Syncing one schedule across devices is exactly what the cloud is good at. The question here is narrower: where does the calendar app run? In a browser tab that loads the page from the web, or as a program on your computer that keeps its own copy?

A calendar has four properties that point to the second answer:

• The data is small. A year of meetings is mostly text: titles, times, guests and links. Keeping a copy on your Mac costs very little.
• It's needed at a precise moment. A calendar earns its place in the minute before a meeting: the reminder, the room, the join link.
• It's personal. Who you meet, where and when is some of the most sensitive data you have.
• It's open all day. You don't open a calendar for one heavy task. You glance at it again and again.

What a browser tab actually costs

Browsers are very good at running untrusted websites safely, and that safety has a cost.

• Each tab is its own process. Chrome renders each tab in a separate process, a model the Electron documentation describes in detail. Chromium's Site Isolation also puts cross-site documents in separate processes. Chromium's own figure for the extra memory was about 10–13% on desktop (Chrome 67) when isolating all sites with many tabs open.
• Tabs compete for memory. Google built Memory Saver to free memory from tabs you aren't using, and says the performance settings let Chrome use up to 40% and 10GB less memory. Inactive tabs are reloaded when you return to them. For a calendar, that's the moment you want it ready. You can exempt sites, but you have to know to do it.
• Desktop wrappers bring the browser with them. In Electron's words, “Electron inherits its multi-process architecture from Chromium”. Each Electron app ships its own copy of that engine.

None of this means Chrome or Electron is badly built. As I wrote in Native vs Electron vs PWA for Mac Apps, memory depends on the specific app and has to be measured, not assumed. The point is structural: a calendar in a tab runs inside a runtime designed for arbitrary websites.

Privacy: who else is in the room

A tab lives in the same browser as your extensions. Chrome's documentation lists the warning people see when an extension asks for broad site access: “Read and change all your data on all websites”. Many extensions request it for good reasons, but it means a calendar tab can be read by more code than the calendar itself.

A native Mac app runs in its own process, and Mac App Store apps run in their own sandbox with their own storage. Sign-in tokens can live in the macOS Keychain instead of browser storage.

In hora, events sync directly between your Mac and Google. Our privacy policy says it plainly: no event, title, attendee or description passes through our infrastructure. Cached data stays inside the app sandbox, OAuth tokens are stored in the macOS Keychain, and anonymous usage counts and crash reports are off by default.

Offline: the meeting that starts on a train

Google Calendar on the web has an offline mode, with conditions. It works only in Chrome, you have to turn it on in Settings first, and it shows events from the last 4 weeks onward. While offline you can't create or edit events, email guests or open tasks. Clearing Chrome's cached files also clears offline support.

A native app can start from a different place. It can keep its own copy of your schedule on disk, so opening it doesn't depend on loading a web page. How much it lets you do without a connection depends on the app, so check before you rely on it.

hora keeps your calendar data locally on your Mac, inside the app sandbox, and it works offline.

Desktop app vs web app at a glance

When a web app is the better choice

Native isn't automatically right. If you check your calendar twice a day, the website is free and perfectly good. Web apps are also the practical choice on a computer you don't own, or when you need the full Google interface, including every Workspace setting.

And if you need iCloud, Exchange and Google in one app, a Google-only client like hora isn't the right fit. The five ways to use Google Calendar on a Mac cover the alternatives, from Dock web apps to multi-provider calendars.

Where hora fits

I built hora because my working day runs on Google Calendar and I didn't want it living in a browser tab. hora is an independent native Mac app that works with Google Calendar. It isn't affiliated with Google. It talks directly to the Google Calendar API, gets push updates when something changes, and shows your day in the menu bar and in desktop widgets as well as in its own window.

Data centers are the right home for heavy, shared work like training and running large AI models. A calendar is the opposite kind of software: light, personal, and needed right now. It's worth a little of your own computer's memory.

Moving from the web version? The step-by-step migration guide covers the switch.

If Google Calendar is where your week lives, try hora Calendar free for 14 days with the Direct download, no card required. After the trial it's $2.99/month, $29.99/year or $59.99 Lifetime.