Same convention as backend/frameworks/: the concepts live in the course note; this is “how this stack does it.”

Not numbered — there’s no reading order. Pick the one you’re using.

The map

FrameworkLanguageApproachBinary sizeStatus
TauriRust + any web frontendOS webview~5–15 MBscaffold
ElectronJS/TS + NodeBundled Chromium~120–200 MBscaffold
QtC++ or Python (PySide/PyQt)Native widgets~15–40 MBscaffold
.NETC#Native (WinUI/MAUI/Avalonia)~20–80 MBscaffold
NativeSwift / C# / C++Platform SDKsSmallestscaffold

Scaffold means scaffold — a page with the shape and the things worth knowing, no written course. The vault’s convention is to say so rather than imply depth that isn’t there.

The axis they differ on

Exactly one thing, and everything else follows from it: where the UI is rendered.

  • Web renderer (Electron, Tauri) → you get CSS, the web ecosystem, and identical rendering everywhere. You pay in memory, and in a look that isn’t native unless you work at it
  • Native widgets (Qt, WinUI, SwiftUI) → you get the platform’s real controls, accessibility and feel for free. You pay in a smaller ecosystem and per-platform quirks
  • Custom-drawn (Avalonia, Flutter, game engines) → identical everywhere, native to nothing, and accessibility is your problem

The accessibility point is underrated. Native widgets are read correctly by screen readers because the OS knows what they are. Custom-drawn UIs must implement accessibility explicitly, and most don’t.

The same concepts, per stack

ConceptElectronTauriQt.NET
UI layerChromiumOS webviewQtWidgets / QMLXAML
Logic layerNode (main process)RustC++ / PythonC#
UI ↔ logicIPC (ipcRenderer)invoke → #[command]signals & slotsdata binding
Packagingelectron-buildertauri buildCQtDeployerdotnet publish
Auto-updateelectron-updaterbuilt-in updaterroll your ownSquirrel / MSIX

Note the shared shape: a UI process and a logic process, talking over IPC. Electron’s main/renderer split and Tauri’s Rust/webview split are the same architecture, and it exists for the same reason as a client and server — the UI must not be able to compromise the privileged side.

That’s also the security model. In Electron, nodeIntegration: false and contextIsolation: true are non-negotiable — the renderer displays untrusted content and must not have filesystem access. Tauri enforces the equivalent by construction: the frontend can only call commands you explicitly expose → web security.

How to add a framework here

Same rule as backend:

  • Which rendering approach, and what it implies
  • How it names the concepts above
  • Its idioms and gotchas
  • What it does badly, honestly

Don’t restate frontend or backend.

↑ Back to Desktop