Join and Run Meetings From the MacBook Notch

#The problem: the call is running, the window is gone

Every video call has the same failure mode. You join, you share your screen or open your notes, and the meeting window slides behind everything else. Then you need to mute fast, or your camera is on when you thought it was off, or the call ran long and you just want to leave, and now you're Mission Control-ing through a dozen windows to find a control that was on screen ten seconds ago. On a laptop with limited screen real estate, the meeting UI is the first thing to get buried.

The fix isn't a bigger window. It's putting the two or three controls you actually reach for somewhere they can't get covered. The MacBook notch is exactly that place: it's pinned to the top center of the built-in display, it's never hidden behind a window, and it's already where your eyes go for system status. That's the same reasoning behind turning the notch into a Dynamic Island in general, applied to the one workflow where a buried window costs you in real time, in front of other people.

#Joining: the calendar Join button

The friction starts before the call does. Your 3:00 is in your calendar, the link is in the invite, and at 2:59 you're digging through Calendar or your inbox to find it. NotchBay reads your calendar (with your permission) and, as a meeting with a video link approaches, surfaces the next meeting in the notch with a Join button right there. One click opens the call in the right place: Zoom's desktop app for a Zoom link, or your browser for a Meet link. You never open Calendar to hunt for the URL.

Because the chip is driven by your actual calendar, it knows which meeting is next and when, so the Join button shows up when it's useful and gets out of the way when it isn't. This is the same calendar activity described in the notch apps roundup, doing the one job that saves you the most fumbling: getting you into the room on time.

#Running the call: mute, camera, leave

Once you're in, the notch switches from a Join button to a compact call control. The three things you reach for most during a live meeting dock beside the camera housing:

• Mute / unmute, the single most time-sensitive control on any call, one click without surfacing the window.
• Camera on / off, so you can drop video for a moment without hunting for the toolbar.
• Leave, to end your part of the call cleanly when it's done.

The important detail is that these aren't a separate mini-app pretending to be your meeting. NotchBay is driving the real Zoom or Meet controls underneath, so the mute state in the notch is the actual mute state of the call. Toggle it in the notch and it toggles in Zoom; toggle it in Zoom and the notch follows.

#How it reaches Zoom and Meet

Zoom and Google Meet are built completely differently, so NotchBay reaches each one its own way. Being honest about the mechanism also explains the limits, so here is the plain version:

Controls reflect what each app exposes. If a meeting app hides or renames a button, the matching notch control can go missing until the app shows it again.

For Zoom, macOS accessibility APIs let one app read and press the controls of another. NotchBay uses them to find Zoom's mute, camera and leave buttons and click them for you, which is exactly what that permission exists for. For Google Meet, there's no desktop app to drive, so NotchBay uses a browser bridge that speaks to the Meet page inside Chromium browsers such as Chrome, Arc, Brave and Edge. Same three controls, a different road to get there.

#Setup: grant accessibility, and why

The setup is short, and each permission maps to exactly one capability so you can see what you're trading:

1. Grant Accessibility. This is the one that unlocks Zoom call controls. macOS gates cross-app control behind the Accessibility permission in System Settings, so pressing Zoom's mute and leave buttons from the notch requires it. Nothing else can drive another app's buttons without it, which is the point: it's a deliberate, revocable grant.
2. Grant Calendar access. This powers the meeting chip and its Join button. Without it, the notch can still run controls once you're in a call, but it won't know a meeting is coming.
3. Use a Chromium browser for Meet. If your Google Meet calls run in Chrome, Arc, Brave or Edge, the browser bridge can reach them. If they run in Safari, open the link in a Chromium browser to get notch controls.

Every permission is optional in the sense that skipping one only costs you that one feature. Skip Accessibility and you lose Zoom controls but keep the calendar Join button; skip Calendar and you keep in-call controls but lose the heads-up. There's no account to create for any of it. NotchBay keeps everything on-device: the only network traffic in the whole app is the Google Drive upload you trigger yourself when you drop a file to share.

#The honest limits

Since I build one of these apps, here's the fair version of what this does and doesn't do today:

• Google Meet needs a Chromium browser. The bridge works in Chrome, Arc, Brave and Edge. Safari is not supported for Meet control right now; if you live in Safari, Zoom's desktop app is the reliable path.
• Controls depend on the app exposing them. The notch drives the real Zoom or Meet UI, so if either app hides a button, reworks its layout, or ships a redesign, a control can temporarily go missing until things are re-mapped. That's the tradeoff of driving the genuine app rather than faking a parallel one.
• It's built for the notch. These activities anchor to the physical cutout on the built-in display, so this is aimed at notched MacBooks running macOS Tahoe (26): any MacBook Pro from 2021 on, and the Air from the M2 in 2022 on.

None of that is unique to me, and I won't pretend it is: the browser-versus-Safari split and the dependence on the underlying app are shared realities for the notch apps that drive calls. Among the notch apps compared in the 2026 roundup, call control at this depth is still a small club, and the mechanics above are the honest reason why.

#Frequently asked questions