DEV Community

Nic Luther
Nic Luther

Posted on

Why We Chose SwiftUI Over Electron for Our Mac App

The Performance Difference Is Staggering

When we started building HeyRobyn, our native Mac unified inbox for email, Slack, and GitHub, we faced a critical architectural decision: should we build with Electron (like most modern desktop apps) or go native with SwiftUI?

The performance numbers made the choice clear:

  • Memory: 50MB (SwiftUI) vs 500MB+ (typical Electron app)
  • Startup time: Instant vs 3-5 seconds
  • CPU usage: Minimal vs constant background activity
  • Battery impact: Native efficiency vs noticeable drain

Why SwiftUI Made Sense for HeyRobyn

1. Native Scrolling and Gestures

One of the first things users notice about HeyRobyn is how it feels like a real Mac app. That's because it is. SwiftUI gives us:

  • Buttery-smooth scrolling powered by macOS's optimized rendering engine
  • Native keyboard shortcuts that respect system preferences
  • Proper support for trackpad gestures (pinch to zoom, swipe navigation)
  • System-level integration (Touch Bar, notifications, Spotlight)

2. Privacy-First Architecture

We built HeyRobyn with a core principle: all your data stays on your device. No cloud sync, no server-side processing. SwiftUI made this natural because:

  • Direct access to macOS security features (Keychain, App Sandbox)
  • No web server running in the background (unlike Electron's Chromium)
  • Native file system access with proper permissions
  • Encrypted storage using Apple's security frameworks

3. Your MacBook's Fans Will Thank You

Electron apps are notorious for spinning up fans and draining batteries. We've all had that meeting where your laptop sounds like a jet engine because Slack and VS Code are fighting for resources.

With SwiftUI, HeyRobyn runs at 50MB RAM — less than a single Chrome tab. Your system monitor will barely register it's running.

The Challenges We Faced

Building native isn't all rainbows. Here's what we had to work through:

Learning curve: SwiftUI is relatively new (2019) compared to web technologies. Finding solutions to niche problems meant diving into Apple's documentation rather than Stack Overflow.

Platform-specific: We can only support macOS. If we wanted to ship on Windows or Linux, we'd need to rebuild from scratch.

Fewer third-party libraries: The npm ecosystem dwarfs Swift Package Manager. We built more components from scratch than we would have with Electron.

Why It's Worth It

Seven days until launch, and we're confident we made the right choice. When users try HeyRobyn, the first thing they notice isn't the features — it's how fast and native it feels.

In 2026, most developers are wrapping websites in Electron and calling them desktop apps. We went the other direction. We built a real Mac app that respects your hardware, your privacy, and your time.

HeyRobyn launches March 18, 2026. First 50 waitlist signups get 50% off forever ($0.50/month). Join at heyrobyn.ai


Building in public, shipping fast. Follow our journey at @heyrobyn

Top comments (0)