Zoom. Meet. Teams. Whatever drives your mic.

Every meeting tool that ships a Zoom integration also ships a Teams integration, a Webex integration, a Meet integration, and a wishlist of the next five. Each integration is its own authentication flow, its own OAuth scope, its own breakage when the vendor changes an API. MeetPing skips that loop entirely by living one layer down: it watches the operating system signals that every meeting app has to drive — the microphone going hot, and the foreground application bundle. When both line up, the listener arms. The vendor on top of those signals is incidental.

The microphone signal comes from Core Audio's kAudioDevicePropertyDeviceIsRunningSomewhere— the same bit macOS reads to draw the orange indicator dot in the menubar. When Zoom opens its mic, that property flips. When Slack starts a huddle, it flips. When you join a Google Meet from a Chrome tab, Chrome opens the mic and it flips. MeetPing reads the bit; it doesn't care which app set it.

Zoom — the native client case

Zoom is the easy case: a native app with a stable bundle ID (us.zoom.xos) that opens the mic the moment you join a meeting. MeetPing sees the mic flip and the Zoom bundle in the foreground at the same instant, arms immediately, and starts feeding both mic and system audio into Parakeet. The first partial transcript lands in about a second and a half — almost always before the host has finished saying hello.

Google Meet — the browser-tab case

Google Meet runs in a tab, which would normally mean MeetPing only sees "Chrome" or "Arc" in the foreground — not specific enough to count as a meeting. We handle that with a Chromium tab-URL fallback: when the foreground app is Chrome, Arc, Brave, Edge, or Vivaldi, we read the active tab URL via the Accessibility API and check whether it's meet.google.com, app.zoom.us, teams.microsoft.com, and a handful of other meeting hosts. Same auto-arm logic, applied to a richer foreground signal.

Microsoft Teams — including the new client

Teams shipped a new native client in 2023 with a fresh bundle ID (com.microsoft.teams2), separate from the classic Electron one (com.microsoft.teams). MeetPing carries both in the default bundle list and arms for whichever your IT department has actually deployed. Calls, meetings, channel huddles — all of them open the mic, so all of them trigger auto-arm.

Slack, Discord, Webex, and the long tail

Slack huddles, Discord voice channels, Webex meetings, GoTo sessions, Around, Whereby — anything that opens the mic and puts a meeting app in the foreground qualifies. The built-in bundle list is editable in Settings → Auto-arm, so if your org uses something exotic (Lifesize, BlueJeans, 8x8), you add the bundle ID once and forget about it. The architecture deliberately has no concept of a "supported" vendor — only of the OS signals that tell us a call is in progress.

For the underlying state machine, see auto-arm. For why we capture both sides of the call, see system audio capture.