desktop

IPC (inter-process communication) in Electron connects your main and renderer processes. Create IPC controllers under apps/desktop/src/main/controllers/, define typed IPC channels, implement corresponding renderer services, and use preload scripts to safely expose APIs. This standardizes bidirectional communication and maintains security boundaries.

Follow a structured layout separating main process controllers, preload scripts, renderer logic, and window management. This guide provides architecture patterns covering file organization, IPC wiring, window creation, and menu configuration to ensure consistent, maintainable development workflows across desktop features.

Preload scripts bridge main and renderer processes safely. Define IPC types, create preload files that expose only necessary APIs, and use context isolation. This prevents renderer code from directly accessing Node.js, protecting your desktop app from injection attacks while enabling controlled feature access.

Yes. The guide covers window creation, menu configuration, and lifecycle management as core patterns. It provides step-by-step implementation for common desktop features, ensuring your menus, dialogs, and windows follow consistent conventions across your Electron application.

Understand the main-renderer process model, IPC fundamentals, and preload script security. This guide assumes basic Node.js and web development knowledge. Start with the Architecture Overview to learn patterns, then implement controllers and services following the structured workflow.

Standardized patterns prevent security issues, reduce bugs, and make code maintainable as your desktop app grows. Consistent IPC wiring, preload configurations, and window management across features speed up development and make onboarding new team members easier.