Rebuilding our Electron recording engine in Swift
Rebuilding our Electron meeting-recording engine in Swift
Circleback's desktop app records meetings without a bot, but the Electron render process proved unreliable for realtime capture. They rebuilt the engine natively with ScreenCaptureKit on macOS and libobs on Windows, tied together by a Swift layer. A custom tool called Atomic automatically bridges Swift's @Published properties to Jotai atoms in React, eliminating manual bindings. The team solved clock drift, driver lies, and crash resilience with fragmented MP4, cutting support tickets dramatically.
A capture engine can't tolerate GC pauses, throttling, or any of the other things a browser runtime does to stay responsive.
- losteric
I really struggle to get past AI writing. Aside from feeling disrespected, something about that style is just so tiring to read… the marketing style of setup and reveal, repetition, only works in small doses
- blululu
I would be curious if the claude wranglers who asked claude to write this piece could ask claude to get some performance data on this in terms of app size, RAM usage and CPU utilization. As the RAM crunch gears up I would really love to AI enabled software development could convert 500MB websites and 1 GB electron apps into performant pieces of software. Agentic coding is just about as good at writing a UI in SwiftUI as it is at writing in React. So there is maybe hope that the software community can take their productivity gains and put them into performant code. Would be interesting to know how much time/effort this project cost and what is the raw benefit to the end user in terms of speed and footprint.
- insane_dreamer
> This is where the macOS engine earns its complexity.
Hi, Claude.