hora Calendar 1.0: The Mac App I Wanted for Google Calendar

I did not start hora because the world needed another calendar app. I started it because I opened Google Calendar in a browser every morning, then spent the rest of the day wishing it behaved like part of my Mac.

The first version of this post was written while 1.0 was still a target. hora reached the Mac App Store on June 30, 2026. Looking back now, a feature inventory feels less useful than explaining what the first release had to prove, what beta users changed, and what I deliberately left out.

If you are comparing every way to use Google Calendar on macOS, start with the broader Google Calendar desktop app guide. This is the story of the narrower product I chose to build.

What hora 1.0 had to prove

I had three tests for the first public release:

1. It had to understand Google Calendar instead of flattening it into a generic calendar model.
2. It had to earn its place on a Mac through native workflows, not only a native-looking window.
3. Its data path had to be simple enough that I could explain it without hiding behind a privacy slogan.

That removed a surprising number of ideas from the roadmap. Version 1.0 did not need every view, integration, or productivity system I could imagine. It needed to make the calendar I already used feel faster, calmer, and easier to trust.

Google-first, not everything-calendar

Many established calendar apps support Google, iCloud, Exchange, Microsoft 365, and CalDAV. That breadth is valuable if your schedule is spread across several providers.

It was not the problem I had.

Google Calendar was already my source of truth. What I wanted was a native client that respected Google-specific details such as event colors, conference links, attendee state, blocking events, multiple accounts, and fast change notifications.

hora connects to the Google Calendar API instead of translating everything through CalDAV. That lets the app stay close to Google's event model and gives me control over synchronization, rate limits, retries, and partial updates.

The tradeoff is intentional. hora 1.0 does not support iCloud, Exchange, or general CalDAV accounts. If you need every provider in one window, a broader calendar app is probably the better choice.

I explained the technical decision in more detail in Google Calendar API vs CalDAV.

The Mac workflows that earned their place

A native calendar should solve moments that a browser tab handles badly.

The most obvious one happens just before a meeting. I do not want to find the right tab, scan an event description, and hunt for a call link. I want to glance at the menu bar and join.

The menu bar in hora shows today and tomorrow, keeps the next event close, and provides a direct route to Google Meet, Zoom, and Microsoft Teams calls. Agenda widgets make the same information available on the desktop without opening the main window.

Keyboard navigation and instant search came from the same principle. If I know what I want to do, the interface should not make me travel through several screens first.

This is why building hora as a native Swift app mattered. Menu bar behavior, widgets, keyboard commands, local caching, drag and drop, and normal Mac window behavior are not decorations around the calendar. Together, they are the product.

There is a longer version of that decision in Native App vs Electron and PWA.

Planning belongs beside the calendar

The first beta began as a faster way to view and edit Google Calendar. It gradually became clear that viewing the schedule was only half of the daily workflow.

The other half is deciding what deserves time before meetings consume it.

Quick Add makes event creation fast enough to stay out of the way. I can type a sentence such as Focus on launch notes tomorrow at 10, check the parsed date and time, and edit the result before saving it.

Focus Time works at a different scale. I drag across one or more visible days, hora removes the time already occupied by events, and a preview shows the focus blocks before anything is created. Share Availability turns selected dates and hours into a message I can paste into email or chat. The Pomodoro timer keeps the execution step close to the plan.

These are not four unrelated productivity tools. They form one loop:

1. Find the time.
2. Protect it.
3. Share the remaining availability.
4. Do the work.

If you are deciding whether that style of planning fits you, I wrote a separate guide to time blocking apps for Mac.

The data path behind hora

Calendar data is personal enough that vague privacy language is not useful. The implementation needs to be understandable too.

Event content is fetched by the app directly from the Google Calendar API and cached locally on the Mac. OAuth tokens are stored in macOS Keychain.

Fast updates require one additional piece. hora registers Google Calendar watch channels. When something changes, a lightweight notification service receives Google's metadata-only notification and forwards a change signal through Apple Push Notification service. The notification does not contain the event body. After receiving the signal, the Mac requests the changed data directly from Google. Periodic sync remains as a safety net.

Google describes this behavior in its Calendar API push notifications documentation.

I used to summarize the architecture as "no servers." I no longer think that wording is precise enough. The notification relay exists, but it does not proxy or store calendar titles, descriptions, attendees, or meeting notes.

The meaningful promise is simpler: there is no hora backend maintaining a second copy of your calendar.

The current data-handling details are documented in the hora privacy policy.

What beta users changed

Before the beta, I thought most of the work left for 1.0 was polishing visible features.

Real calendars corrected that assumption quickly.

Testers brought accounts with years of history, several calendars, recurring meetings, unusual colors, invitations in strange states, and changes arriving seconds before a call. Large accounts exposed quota behavior that did not appear in my own setup. Dragging, resizing, deleting, and moving through the calendar revealed states that a happy-path demo never reached.

That feedback shifted time away from adding more features and toward less visible work:

• Better rate-limit recovery and request pacing.
• More reliable synchronization after sleep or a lost connection.
• Consistent event state across the main window, menu bar, and widgets.
• Deep links that open the event you actually selected.
• Safer handling of invitations, recurring events, and partial updates.

The first public beta retrospective contains more of those details.

The lesson was not subtle. A calendar app can look finished and still be untrustworthy. Version 1.0 had to be boring in the places where boring means reliable.

What I deliberately left out

hora 1.0 does not try to replace every calendar for every person.

It does not combine Google Calendar with iCloud and Exchange. It does not turn the schedule into a project-management dashboard. It does not ask an AI model to reorganize the week automatically.

On supported configurations, optional on-device Foundation Models can polish an event title or availability message, name a focus block, or summarize an existing description. Each workflow still has a deterministic fallback. AI is a small convenience inside the calendar, not the reason the calendar exists.

That restraint is part of the product. Supporting fewer systems lets me spend more time on the details Google Calendar users encounter every day.

Who hora Calendar 1.0 is for

hora is for you if Google Calendar is already the center of your schedule and you want:

• A native Mac app instead of another permanent browser tab.
• Fast access to the next event from the menu bar or desktop.
• Google-specific event behavior without a CalDAV translation layer.
• Keyboard-friendly planning, Quick Add, and focus scheduling.
• A clear data path in which event content moves between your Mac and Google.

It is probably not the right fit if your work depends on combining several calendar providers in one app. Apple Calendar, Fantastical, or BusyCal may serve that setup better.

You can review the complete current feature set on the hora features page.

Try hora Calendar on the Mac App Store

Version 1.0 did not mean the app was finished. It meant the original idea had survived contact with real calendars and real users.

Google Calendar remains the source of truth. hora is the Mac layer I wanted around it.