spa-routes

A blank screen in your SPA often stems from route-registration drift, where updates aren't mirrored across the desktop router config pair, causing navigation failures. You must apply identical RouteObject structure changes to both config files to prevent this.

To organize React routing correctly, keep the src/routes/ layer thin by limiting it to segment entry and layout wrappers. All real UI and domain business logic must be implemented under the src/features/ directory.

The best way to refactor SPA route segments safely is to progressively migrate logic into src/features/ by domain while ensuring src/routes/ remains a thin wrapper. Any route tree structure change must be mirrored across the desktop router config pair.

Handle desktop and mobile router differences by mirroring identical RouteObject structures across the desktop router config pair. This prevents registration drift and ensures consistent navigation behavior when modifying the SPA route tree.

No, you should not place domain business logic in React route files. The src/routes/ directory must remain a thin layer for segment entry and layout wrappers, while real UI and business logic resides under src/features/.

You should update both desktop router config files whenever the SPA route tree structure changes. Mirroring the RouteObject structure across the config pair prevents registration drift and avoids blank-screen navigation failures.