983: Why I Chose Electron Over Native (And I’d Do It Again)

What It Covers

Scott Tolinski built a custom screen recording desktop app called VFramer using Electron after abandoning Tauri, solving core problems with existing tools: proprietary file formats, 45-minute post-processing times, data loss on crashes, and inability to record multiple independent sources simultaneously as raw MKV files.

Key Questions Answered

• •Tauri vs Electron for media apps: Tauri's WKWebView on macOS blocks retina-resolution screen recordings and lacks certain media capture dialog support, making it unsuitable for high-quality screen capture tools. Electron's Chromium engine delivers consistent, predictable behavior across OS versions — critical when accessing low-level hardware APIs like screen capture, Bluetooth, and MIDI that Safari simply does not expose.
• •MKV format eliminates post-processing time: Recording to MKV via WebM segments avoids the 45-minute export wait that plagues tools like ScreenFlow and iShowU. MKV files are append-only by design, meaning no finalization process is required. If the app crashes mid-session, all recorded segments remain intact and can be reprocessed individually without any data loss.
• •License key distribution without a SaaS backend: A one-time purchase flow using Stripe webhooks → Cloudflare Worker → self-hosted Keygen.sh server generates and emails license keys automatically. Self-hosting Keygen via Docker on Coolify eliminates recurring SaaS fees. The app validates keys locally, enabling offline use — a critical requirement for desktop software sold outside the Mac App Store.
• •Electron auto-updates via R2 bucket: Using electron-updater pointed at a Cloudflare R2 bucket, combined with GitHub Actions CI/CD that handles Apple notarization and code signing on every release build, delivers seamless background updates. Users receive a native macOS dialog on next relaunch rather than manually downloading and reinstalling a DMG file each version.
• •Browser MediaRecorder API smooths hardware inconsistencies: Using `getUserMedia` in Electron's Chromium layer abstracts away device-level quirks — mismatched frame rates, unusual microphone drivers, codec incompatibilities — that surface when calling native OS APIs directly. This approach also keeps the codebase cross-platform, requiring no OS-specific code paths for Windows or Linux support in future releases.