Where React Earns Its Place
Interfaces people work in rather than read: dashboards, portals, planners, anything with state that should persist while somebody moves around.
The value is that the screen updates without reloading, so an application feels immediate rather than like a series of page loads. For somebody spending an hour in a system, that is the difference between a tool they tolerate and one they like.
It also brings components, which is where the commercial benefit sits: build a table once, use it everywhere, fix it once. Interfaces assembled from shared parts stay coherent as they grow and cost far less to change.
When A Page Reload Is Genuinely Fine
Worth saying, because React gets applied where it adds cost and nothing else.
A brochure site does not need it. A form somebody fills in once does not need it. Content that should be found in search is actively harmed by it, because pages assembled in the browser are seen less reliably and less often by crawlers, and a first-time visitor waits for code to load before seeing anything.
The split that works: public pages rendered on the server so they are fast and findable, application screens behind the login built in React. Applying one approach everywhere is where the expensive mistakes happen in both directions.
What Moves The Price
How many distinct screens, and how much they share. A design built from reusable elements is dramatically cheaper to implement than one where every screen is drawn separately.
Data density. Tables with sorting, filtering, inline editing and pagination are more work than they look, and they are what business applications are mostly made of.
Whether it must work well on mobile, which is a design constraint rather than a scaling exercise.
Real-time requirements. Live updates across users add infrastructure.
Accessibility requirements, which are easier designed in than retrofitted.
Where React Projects Go Wrong
Components that exist but are not reused. A shared library alongside a codebase full of near-duplicates: the maintenance overhead with none of the benefit. The symptom is visible to you, as similar things behaving slightly differently in different places.
State scattered everywhere. The most common cause of bugs where the screen shows something the data does not.
Applying it to public pages and losing search visibility.
Design handed over as screens rather than a system. Individually drawn screens produce individually built screens and consistency drifts immediately.
Questions To Ask Whoever Builds It
- Is there a shared component set, and is it actually used? Both halves.
- If we changed our brand colours, how long? Hours in a good build, weeks in a duplicated one.
- Which pages are public, and are those server-rendered?
- How does this behave on a phone?
- What happens if the JavaScript fails to load? For anything public, there should be an answer.
A Brief You Can Send Anyone
What the interface is for: [the work people do in it]
Who uses it: [and how often; frequent users justify more]
The main screens: [three or four, described]
Data volumes on screen: [ten rows or ten thousand]
Public or behind a login: [per area]
Devices: [desktop, tablet, phone, and where]
Design status: [none, screens, or a system]
How We Build It
React for the application, server-rendered for anything public, a small shared component set used everywhere rather than admired from a distance, and a single place where the design values live so a change is one change.
Where the interface is the whole product, web application development covers the wider build. Get in touch with what people need to do on screen.