Building Desktop Applications with Electron
summary
Electron bundles Chromium + Node.js runtime to let web code run as desktop apps, splitting work into a main (Node-enabled) process and multiple renderer (Chromium UI) processes that talk via IPC. Key APIs include autoUpdater, dialog, tray and touch bar; native needs use node-gyp or electron-rebuild for C/C++ modules. Security advice stresses disable nodeIntegration, use CSP and context isolation. Microsoft uses Electron with React to ship Skype on Windows, macOS and Linux; tradeoffs are large bundle size and higher memory per renderer.
AI-written summary · about
chapters (32)
- 0:00Start
- 0:27Roadmap
- 0:38Features of Electron
- 1:18What Is Electron
- 2:13Contributors
- 3:05What Desktop Applications Offer Different than Web Applications
- 3:29Notifications
- 4:37Chromium and Nodejs
- 6:56Renderer
- 7:19Chromium Api
- 7:36First Electron App
- 8:02Main Components
- 10:02Lifecycle Manager
- 13:55The Electron Api
- 14:56Power Monitor
- 19:11Troubleshooting
- 20:35Security
- 21:43Checklist
- 22:01Context Isolation
- 22:43Microsoft and Electron
- 23:23Electron Mini Summits
- 23:48Core Summit
- 24:11Microsoft Teams
- 24:25Chromium Upgrades
- 25:19What Did You Learn
- 26:34Electron Community
- 26:51The Future of Electron
- 27:35Modularity of Electron
- 28:36Pros and Cons
- 30:31Pros
- 32:22Skype Client
- 34:35Questions
related talks
58mCross-Platform Desktop Apps with Electron
01h 01mElectron - Writing desktop applications using web technologies
54mCross-Platform Desktop Apps with Electron
25mElectron: Desktop Apps with JavaScript
23mHow to Electron
21mBuilding Cross Platform Desktop App using Web Technologies with Electron
17mBuild Your Next App with Electron
44mApplication Development with Electron: How and Why