electron-fsd

Structure an Electron app with Feature-Sliced Design by dividing the Renderer into shared, entities, features, widgets, and pages layers, while isolating Main and Preload process logic to enforce clear IPC boundaries and scalable folder conventions.

FSD layer responsibilities assign READ operations to entities, CUD actions to features, composition to widgets, routing to pages, and shared utilities to the shared layer, enforcing strict slice boundaries and public API exports across the Electron renderer.

Establish clear IPC boundaries in an Electron application by separating the three-process model into Main, Preload, and Renderer, applying routing conventions and strict slice boundaries to prevent direct cross-process imports and maintain public API patterns.

Yes, you can use Feature-Sliced Design with React 19 in an Electron project by structuring the Renderer process into FSD slices and applying naming conventions, public API exports, and strict layer separation for scalable, maintainable apps.

Use FSD for Electron renderer architecture instead of a flat folder structure to enforce strict slice boundaries, standardized public API exports, and clear layer responsibilities, which prevents circular dependencies and ensures scalable, maintainable project growth.

The recommended project layout for a scalable Electron app divides folders into Main, Preload, and Renderer, then further divides the Renderer into entities, features, widgets, pages, and shared layers with enforced naming conventions and public API exports.