desktop

Electron desktop app architecture separates concerns into the main process for window lifecycle, the renderer for UI, and preload scripts for secure context bridge isolation. This pattern ensures secure IPC communication and robust desktop application structure.

The best way to implement IPC communication in Electron is by using a controller-service pattern. Define IPC types, create a controller to handle main process requests, implement corresponding services for business logic, and invoke store actions to manage state orchestration.

Window lifecycle and menu integration in Electron are configured within the main process. You manage window creation, visibility, and destruction events while attaching native menus, following best practices for cross-platform desktop UX and performance optimization.

To secure preload scripts in Electron, expose only necessary APIs via contextBridge with strict parameter validation. Avoid exposing Node.js modules directly to the renderer process to prevent remote code execution and maintain desktop application security.

To add a feature, create a controller under src/main/controllers, define IPC types in the shared types file, implement a corresponding service in src/services/electron, add a store action to invoke it, and write unit tests under the controller's test directory to verify behavior.