Electron — desktop apps for macOS, Windows & Linux

Why I use it

When a tool needs the filesystem, a tray icon or a global shortcut, the browser can't help you and a native rewrite per platform is rarely worth it. Electron's cost is memory and bundle size, and that's a fair criticism. The part people get wrong is the security model: context isolation on, node integration off in the renderer, and a preload script exposing a narrow typed API over IPC. Skip that and a rendered web page is one XSS away from the user's disk.

What I've built with it

• Desktop tools packaged and code-signed for macOS, Windows and Linux from a single codebase
• Main and renderer processes kept properly separated, with context isolation on and privileged work behind a typed IPC surface
• Native integrations the web can't reach — filesystem access, tray icons, global shortcuts, auto-update

Alongside

Rest of the stack

• React.jsComponent-driven web UIs
• Next.jsApp Router, SSR & static rendering
• React NativeOne codebase, iOS + Android
• Node.jsAPIs, services & tooling
• ExpoBuild, OTA update & ship RN
• TypeScriptStrict types across every layer
• GraphQLTyped APIs, one query per screen
• FirebaseAuth, Firestore & push
• SupabasePostgres, auth & storage
• DockerReproducible builds & environments