Framework choice is usually developer preference dressed up as strategy, and I say that as someone whose default has been Next.js for years. The reasons I would give another developer are not the reasons that matter to the person paying for the project, and the gap between those two lists is worth writing down, because the second list is the one that survives contact with a budget.
The problem it solves is a rendering problem, not a framework problem
A plain React application renders in the browser. The visitor downloads a JavaScript bundle, the bundle runs, and only then does content appear. Behind a login that is completely fine and often the right architecture. For anything that needs to be found, it is bad, because the first thing a crawler or a three-year-old phone receives is an empty document with a script tag in it.
The standard answer is to bolt server rendering onto React by hand. That is not a weekend.…