Choose React for interaction complexity
A content-led website does not need a client-heavy application by default. We use React when reusable stateful interfaces create a clear product benefit.
Model the awkward states
Loading, empty results, permissions, validation, slow networks and recovery paths are part of the implementation, not exceptions left for later.
Keep the client bundle accountable
Server rendering, code boundaries and dependency choices are reviewed so the framework does not become an excuse for avoidable JavaScript.