architecture

Structure an Electron app by organizing code into distinct layers: src/renderer for UI, src/process for main and services, and src/common for shared types. This enforces correct code placement and clear process boundaries.

Organize IPC bridges and shared utilities in a multiprocess Electron project by applying consistent directory layout and naming conventions. Place cross-process communication logic in dedicated layers to ensure safe and organized boundaries.

Scale an Electron project architecture by following structured guidance for adding new bridges, services, or workers. This ensures organized directory structure and safe cross-process communication during future expansions.

Enforce coding standards for Electron cross-process communication when starting a new project or expanding existing ones. It clarifies where UI, main logic, and bridges belong, preventing complex and error-prone architecture decisions.

Yes, this architecture guidance applies to both new and existing Electron app migrations. It guides future expansions and migrations by ensuring correct placement of code and responsibilities across renderer, process, and shared layers.