Stackologists · when the repo is already React
React when the public HTML has to be the product
Stackologists treats React as a library and publishing as a separate decision. We build React work that ships with the answer already in the document.
We use React and Vite for product UI and for public sites that should be readable on the first request. That is the difference between a tool the team likes and a page a customer can find. If search is part of the job, we decide the render plan before we write the first component.
When we pick React
- A product UI that the team will keep in JavaScript.
- A marketing or research surface that can be prerendered.
- A migration off a client-only shell that search cannot see.
When we pick something else
A C# team with no JavaScript owners should read the Blazor page. A long-lived enterprise app with an Angular estate should stay on Angular unless you have a reason that is not boredom.