What's this about?
Baoyu described making his video-editing app cross-platform. He started on Electron, but pure web technology struggled with video editing — long videos with many subtitles caused severe lag and enormous memory use. He built a Mac version in Swift and AppKit using Fable 5, and said the result matched the design mockups almost exactly, adding that Fable 5 is the strongest model at reproducing UI from a design, bar none. For cross-platform support he then built a Rust command-line core as a proof of concept, where audio transcription and video export outperformed the Swift version while also running on Windows, and is now porting the Swift interface on top of it — noting that the more features you build first, the more painful the migration.
What exactly is GPUI?
GPUI is the interface framework the Zed editor team wrote in Rust, which draws the entire application using the graphics card rather than the web rendering engine most desktop apps rely on. Electron, the dominant alternative, effectively ships a whole browser inside your app — convenient and cross-platform, but heavy on memory and weak when the work is genuinely computational, like editing video. GPUI trades ease of development for native performance.
Why is this worth noticing?
- It's a concrete, unsponsored data point on model capability: a developer reporting that a specific model reproduces design mockups better than alternatives is more informative than a benchmark score.
- The migration lesson is broadly applicable — the cost of moving platforms scales with how much you built before deciding, which argues for settling the architecture question early even when AI makes the first version cheap.
- It's the second Rust + GPUI story in two days, after Waku's launch, suggesting the framework is escaping Zed and becoming a genuine option for performance-sensitive desktop apps.