PROVIDER Β· desktop apps built with web technology
Electron
Electron bundles Chromium with Node.js so HTML, CSS, and JS produce cross-platform desktop apps, powering VS Code, Slack, and Figma desktop as the fastest route for frontend teams into desktop.
Pros
Cons
Product Information
Detailed Notes
Overview
Electron was created by GitHub in 2013 initially for the Atom editor, bundling the Chromium engine with the Node.js runtime so interfaces are written in HTML, CSS, and JS with filesystem and system API access, producing Windows, macOS, and Linux apps from one codebase.
For Programming Languages & Frameworks work the value is reusing frontend skills for desktop, since VS Code, Slack, Discord, and Figma's desktop app run on Electron, teams with a web stack gain cross-platform desktop fastest, and the ecosystem from electron-builder to electron-updater is mature.
Face the costs, because apps are large often exceeding a hundred megabytes with high memory use since each ships Chromium, startup trails native apps, the attack surface is wider requiring contextIsolation and disabled nodeIntegration, and performance-sensitive desktop tools fit Tauri better.
Core Strengths
- Reuses HTML, CSS, and JS so frontend teams build desktop apps directly
- One codebase targets Windows, macOS, and Linux
- A mature ecosystem covers packaging, code signing, auto-update, and crash reporting
- Full Chromium rendering keeps complex interfaces consistent
Product Ecosystem
Process model
The main process manages windows and system access while renderers run interfaces communicating over IPC with preload scripts.
Packaging
electron-builder or forge produce installers with electron-updater handling incremental updates.
Engineering
Pairs with Vite, React, and Vue and tests end to end through Playwright.
Drawbacks
- Large packages often above 100MB hurting download and install
- High memory use as each app bundles Chromium
- Slower startup than native apps
- A wider attack surface requiring careful isolation
Use Cases
- Web teams shipping desktop (β β β β β ) - Reuse existing skills
- Turning internal tools into desktop apps (β β β β β ) - Short cycles
- Cross-platform rich editors (β β β β ) - Mature ecosystem
- Light high-performance desktop tools (β β ) - Consider Tauri
Pricing
| Plan | Price | Scope |
|---|---|---|
| Electron | $0 | MIT licensed, free |
| Packaging tools | $0 | Open source and free |
| Code signing certificates | About USD 100-400 annually | Required for Windows and macOS releases |
The framework is free with cost in code signing certificates around a hundred dollars yearly and distribution bandwidth given large installers, while internal distribution can skip signing at the price of security warnings.
FAQ
-
Electron or Tauri? Electron for full Chromium consistency and a mature ecosystem, Tauri for smaller size, lower memory, and a tighter security boundary.
-
How is size reduced? Use ASAR packaging, prune dependencies, split locales, or switch to system WebView approaches like Tauri.
-
How is security ensured? Enable contextIsolation and sandbox, disable nodeIntegration, expose minimal APIs through preload, and keep Electron updated.
Code Examples
Minimal main process
const { app, BrowserWindow } = require('electron');
app.whenReady().then(() => {
const win = new BrowserWindow({ width: 1200, height: 800 });
win.loadURL('https://16idc.com');
win.webContents.openDevTools();
});
Point main in package.json at this file and run npx electron ..
IPC between renderer and main
// preload.js
const { contextBridge, ipcRenderer } = require('electron');
contextBridge.exposeInMainWorld('api', {
version: () => ipcRenderer.invoke('app:version'),
});
// main.js
ipcMain.handle('app:version', () => app.getVersion());
Keep context isolation on and expose an allowlist through preload rather than full Node access.
Community & Resources
Communities and official channels
- Electron Docs β Processes and the security guide
- GitHub electron/electron β Source, issues, and releases
- Electron Discord β Official community channels
Learning resources and tools
- Electron Forge β Official packaging toolchain
- electron-builder β Another mainstream packager
- Awesome Electron β Curated apps and libraries