title: Is it best to use Next.js along with ASP.NET Core web api if SSR is not the target?
body: <p>I am looking into React framework Next.js to see if it is best match as SPA for my next application where ASP.NET Core will be backend. I have used <code>create-react-app</code> in the past so wanted to compare <code>Next.js</code> with it. Our aim is not <code>Server Side Rendering(SSR)</code>. Our project will be admin kind of project and SEO does not really matter. We will need performance for sure. We cannot use Static Generation as well as we need to load latest data for every page. We will need redux too.</p>
  <p>The main benefits I read about Next.js are:</p>
  <ul>
  <li>SSR</li>
  <li>File Routing</li>
  <li>Full stack Dev - can use backend(Node.JS) with it</li>
  </ul>
  <p>From these mentioned feature, File Routing will only be useful for us I believe as we don't need other features for our project. Further more, I cannot see any component life cycle events. Can we still use it with Next.js?</p>
  <p>Can anyone please highlight other benefits of using Next.js? And is it worth to use <code>Next.js</code> over <code>create-react-app</code>?</p>