● Covered by 1 source · 1 reportLow impact1 neutral
Company rebuilds Electron meeting-recording engine in Swift for improved reliability
Key points
- Recording engine moved from Electron render process to native Swift.
- Uses ScreenCaptureKit (macOS) and libobs (Windows) for capture.
- Developed Atomic tool for Swift-to-React (Jotai) data binding.
- Atomic provides type-safe, reactive communication without manual bindings.
Addressing Electron's Limitations
The company's desktop application, designed for bot-free meeting capture and cloud streaming, faced persistent reliability issues with its Electron-based recording engine. The engine, running within Electron's render process, was susceptible to garbage collection pauses and throttling, which are detrimental to real-time audio and video capture. Attempts to fix these issues through lifecycle management and thread offloading provided only marginal improvements.
Transition to Native Technologies
To achieve greater reliability, the recording engine was rebuilt using native technologies. On macOS, ScreenCaptureKit is employed, while Windows utilizes libobs. A shared Swift layer integrates these platform-specific components, providing a more stable foundation for the capture process. This native approach bypasses the performance constraints of the Electron render process.
Introducing Atomic for Cross-Platform Bridging
To facilitate communication between the native Swift runtime and the React frontend, the company developed an internal tool named Atomic. This tool automatically converts Swift's @Published properties into Jotai atoms in React, creating a fully reactive and type-safe bridge. This eliminates the need for manual native addon bindings, which are prone to errors and difficult to maintain.
Seamless Data Flow and Type Safety
Atomic uses a @NodeExport macro to generate the entire bridge at compile time, ensuring automatic type mapping between Swift and TypeScript. Value changes in Swift trigger callbacks on Node's event loop, and new Swift properties become immediately available in React. The tool is built on Swift and OpenCombine, allowing it to function consistently across both macOS and Windows platforms.
✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →
The daily brief
One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.
One email a day. Unsubscribe in one click, any time.
Today's brief
Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.
▶ Play today's brief
New every morning, and the back catalogue is archived by date.
Primary sources
GitHub OpenCombine/OpenCombineReporting from
A company migrated its Electron-based meeting recording engine to Swift, utilizing native APIs like ScreenCaptureKit and libobs, to address reliability issues caused by Electron's render process limitations. This shift improved real-time audio and video capture performance by avoiding garbage collection pauses and throttling inherent in browser runtimes. The company also developed an internal tool called Atomic to bridge Swift properties with React's Jotai atoms, enabling type-safe and reactive communication between native and web components.