Your next meeting, dropped over every screen.
Website · Privacy Policy · Terms of Service
A macOS menu bar app that shows your next Google Calendar meeting and, shortly before it starts, cuts in: it covers every screen until you join the meeting or deliberately dismiss it.
cut-in.mp4
- Several Google accounts at once; an event you were invited to from more than one account appears once.
- The menu bar shows the next meeting and a countdown (
Weekly sync · in 12m). - The menu lists today's and tomorrow's meetings, coloured by account. Each opens a submenu with its time, place, people and description, and actions to join its Meet, Zoom, Teams or Webex link, copy the link, or open the event in Google Calendar.
- Optionally, a month or a week above the meetings in the menu; choosing a day lists its meetings.
- The cut-in appears
nminutes before the start (configurable, default 2) on every display. Plugging or unplugging a display or changing the resolution rebuilds it to fit the new screens. - It stays until you press Join Meeting (or Return) or press and hold the small dismiss control in the bottom-left corner. In an emergency, ⌃⌥⌘⎋ (Control-Option-Command-Escape) dismisses it too. Escape alone and ⌘W do nothing.
Calendrop is strongly inspired by MeetingBar, a menu bar app that keeps your next meeting in sight and joins it in one click.
The difference is where the full-screen reminder sits. In MeetingBar it is one reminder among several: off by default, next to the macOS notifications, with little to adjust. In Calendrop the cut-in is the app itself, and everything else is there to make it hard to miss and easy to act on. Calendrop was built as a separate app for that, and for what MeetingBar 4.11 did not do for us:
- Its Google Calendar connection takes one Google account. Calendrop reads several at once and merges them into one timeline.
- Its full-screen reminder appears on one display, and could be left off-screen and impossible to close when that display was unplugged. Calendrop's cut-in covers every display and is rebuilt whenever the screens change.
Requires macOS 14+ on Apple silicon. With Homebrew:
brew install --cask calendrop-app/tap/calendropOr download Calendrop-<version>-macos-arm64.zip
from Releases, unzip it
and move Calendrop.app into /Applications. The app is self-signed, not
notarized, so the first launch has to be allowed in System Settings › Privacy
& Security.
To build it yourself instead, with Xcode (the Command Line Tools cannot compile its translations):
just install-macos # build Calendrop.app and copy it into /ApplicationsA build made without the Google OAuth client (see below) cannot sign in to real accounts. It starts with sample accounts instead, with sample calendars and meetings, and Add Account… adds more, so everything else — labels, colours, calendar choice, the menu and the cut-in — can be tried. Nothing is saved: sample accounts and any settings changed are forgotten when Calendrop quits, and the settings shared through iCloud are never touched.
Open Settings → Accounts, press Add Account…, and sign in in the browser. Repeat for each Google account.
Sign-in needs a Google OAuth client embedded in the app. A build without one offers sample accounts instead (see above). Whoever builds Calendrop sets one up once:
- In Google Cloud Console, create a project and enable the Google Calendar API.
- Configure the OAuth consent screen. While its publishing status is Testing, only listed test users can sign in and Google expires their sign-in after seven days; publish it to In production to avoid that (unverified apps show a warning and are limited to 100 users).
- Create an OAuth client ID of type Desktop app.
Then pass its ID and secret to the build through the environment; just bundle (and just run, just install-macos) embed them:
CALENDROP_GOOGLE_CLIENT_ID=… CALENDROP_GOOGLE_CLIENT_SECRET=… just install-macosKeep them out of the repository — for example in a password manager whose CLI
can inject them, such as op run for 1Password. Google treats a Desktop
client's secret as non-confidential: the loopback redirect, PKCE and the
user's own consent protect each sign-in.
Calendrop keeps two kinds of state apart:
| What | Where | Shared |
|---|---|---|
| Account list, lead time, cut-in style | ~/Library/Mobile Documents/com~apple~CloudDocs/Calendrop/config.json (iCloud Drive), or ~/Library/Application Support/Calendrop/ without iCloud Drive |
yes |
| Refresh tokens | login Keychain, non-synchronizable, this device only | no |
On another Mac the accounts appear as "Sign-in required". Signing in opens the
browser with the account already chosen (login_hint), so tokens never travel
between machines.
Builds are signed with a self-signed identity, "Calendrop Release", when the login
keychain has it, so every build has the same signing requirement. Make it once with
just release-identity <folder>, keep the two values it prints, and import them
on each Mac:
CALENDROP_SIGNING_P12=… CALENDROP_SIGNING_PASSWORD=… just import-identityWithout it, builds are signed ad-hoc.
Either way, macOS asks for Keychain access once more after each rebuild or update, even when it was always allowed: without an Apple team ID in the signature, it ties that answer to the build itself.
Publish a GitHub release tagged vX.Y.Z. The version comes from the tag alone:
Resources/Info.plist keeps 0.0.0, and the Release workflow writes X.Y.Z
into the app it builds. The Release workflow builds the app
from the tag, signed by "Calendrop Release" and with the Google OAuth client
from the environment "release", and attaches the zip to the release. It then
has the site rebuilt and the
Homebrew cask rewritten for the
release, through the tokens in the secrets SITE_DISPATCH_TOKEN and
HOMEBREW_TAP_DISPATCH_TOKEN.
Enter the development shell with nix develop (or copy .envrc.sample to
.envrc and direnv allow) for just, nixfmt and rsvg-convert. Swift itself comes from
Xcode. Then:
just fmt # format every source
just l10n # add the strings the source uses to the String Catalogs
just ci # everything CI runs: format check, warnings-as-errors build, catalog check, tests
just run # build build/Calendrop.app and launch itThe design lives in docs/concept.md, the decisions behind it in docs/adr/, and the behaviour it promises in docs/spec/.
MIT. See LICENSE.