Building Cross Platform Desktop Apps With Electron
summary
Electron is Chromium plus Node.js so web UI gets desktop file‑system power; many apps (Slack, VS Code, Atom) prove the approach works. Heavy CPU work runs best in hidden browser windows rather than main or web workers. Native C/C++ add‑ons (about 400 of ~650k npm packages) force per‑platform compilation and complicate packaging and code signing (Mac apps must be signed on a Mac, Windows on Windows). For security disable nodeIntegration for remote content, use a preload bridge, handle permission requests, and avoid eval.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:34Life Before Electron
- 4:10Electron Architecture
- 9:01Multithreading
- 11:12Hidden Browser Window
- 14:33Native Modules
- 15:38Solution?
- 17:25Code Signing
- 20:13Security for loading remote content
- 25:32require() calls are costly
related talks
29mFast, Cross-Platform Desktop Apps with Electron
58mCross-Platform Desktop Apps with Electron
22mBuilding Desktop Applications with Node and Electron
21mBuilding Cross Platform Desktop App using Web Technologies with Electron
34mReal world Electron: Building Cross-platform desktop apps with JavaScript
26mNode on the Desktop: Building Apps with Electron v1
25mNode.js for desktop development (based on Electron library)
36mElectron JS - desktop applications written in JavaScript
