architecture

To structure a multi-process Electron app, standardize your project layout by enforcing directory rules and naming conventions that clearly separate renderer, main, and worker code, including bridges, services, and agents. This maintains consistency when adding new modules.

The best way to organize Electron renderer and main process code is by applying a prescribed directory layout that maps specific process folders, ensuring a clear division of bridges and services across the codebase to reduce confusion.

You should place new bridges and services in an Electron project by following documented directory layout rules and naming conventions, providing a clear mapping for each module to maintain structural consistency across processes.

Yes, you can use these architecture guidelines to refactor single-file components into structured directories. It helps teams evaluate conversions and enforces test mappings for multi-process Electron applications.

You need specific directory layout rules for Electron workers when your project requires a clear division of worker code from main and renderer processes, reducing confusion when adding new workers or services to the codebase.