When we reach for it
Interfaces with real state in them, and any front end a client will need to staff after we hand it over. The ecosystem is the argument as much as the library is.
Web and application frameworks
React development
The component model most of the industry has standardised on, with the deepest hiring pool and the longest operational track record of any front-end library.
What we reach for first
When we would argue against it
It is too much machinery for a page that could be HTML and a stylesheet. We do not ship a component tree to render text a server could have sent finished.
What it looks like in delivery
We keep state as close to where it is used as possible, treat the server as the default place for rendering, and reach for a client component when there is an interaction that genuinely needs one. Most performance problems we are called in to fix are architectural rather than React’s fault.
Where this appears on the site
Published work that names it
- Rebuilding subscription billing and entitlements at SalteaCase study · architecture
- Making offline receipt capture reliable in Vertigem's expense platformCase study · architecture
- Web developmentService · stack
Derived from the stacks published on those pages, not written here — so this list cannot claim something the page it points at does not say.
Working in React?
Tell us what it is running, what it costs you today, and what you need it to do next. A senior engineer will tell you what we would keep and what we would change.