React for application interfaces that consume APIs

React is a library for building application interfaces that consume APIs. It is not a backend or a complete framework: rendering, state, routing and tooling are chosen separately. It fits when the interface has interaction and state that server-rendered HTML does not handle well.

Tell us what you need

Level 3 · Build · Quoted per project · React + TypeScript + API

If this is happening to you

  • 01The interface combines states —filters, multi-select, forms with dependencies— and every change means a reload or a patch to the served HTML.
  • 02There is a dashboard or internal panel with data that changes and views that should share components, yet each screen is maintained on its own.
  • 03The product behaves like an application: people expect an immediate response without losing the context of what they were doing.
  • 04The data comes from a first- or third-party API, and static HTML is not enough for the interaction the screen calls for.

The list is not exhaustive: if the requirement is another, the decision is made the same way.

Page content
  1. 01The problem it solves
  2. 02When it adds value and when it doesn't
  3. 03What we do
  4. 04Performance and maintenance
  5. 05Proof: stated capability
  6. 06Frequently asked questions
  7. 07Related services

01The problem it solves

React is not a complete framework. Choosing the library is the easy part; after that come the router, rendering, state, build and tests, and each piece has to be maintained.

Each of those decisions has a cost. A poorly chosen rendering strategy leaves the HTML empty or duplicates logic; an uncontrolled JavaScript budget makes the interface slow to respond even when the server is fine.

The interface does not fix a confused backend either. If the API returns contradictory states or has no contract, React only makes that visible in the interface.

An interface does not replace a data contract

If the API has no clear rules about what it returns in each state, building the screen first pushes that ambiguity into the components. The contract is agreed before the first view.

02When it adds value and when it doesn't

Can add value

  • Interface state is complex: combined filters, multi-select or long forms with dependencies between fields.
  • There are dashboards or internal panels with changing data and views that combine without reloading the page.
  • The product is interactive and needs an application interface, not a content page.
  • A first- or third-party API serves the data and static HTML is not enough for the interaction.
  • A JS/TS team can maintain components, dependencies and the build.
  • The goal is to reuse components and apply a design system in a real application.

Doesn't add value

  • It is a content-first corporate website: the PHP theme with Gutenberg is simpler and more predictable.
  • The team does not work with JS/TS and cannot take on dependencies, build and updates.
  • The site is mostly content and the served HTML already handles the interaction it needs.
  • React is added because it is fashionable, with no interface need to justify it.
  • The project is headless with WordPress and Next.js: that decision belongs to its own page, not this one.
  • No rendering strategy, accessibility plan or JavaScript budget has been defined.

The four decisions

  1. 01

    Stay with the WordPress theme

    If the site is a content-first corporate website and the interaction fits in Gutenberg and a PHP theme, React is not needed. Served HTML is simpler to maintain and requires neither a build nor npm dependencies.

  2. 02

    React for part of the interface

    When only one screen needs real interaction —a configurator, a panel, a long form—, React can live alongside the rest of the site without rewriting it. The component has to be isolated and you accept two ways of building and deploying.

  3. 03

    React with its own API

    If the whole product is an application with several views and shared state, React with an API behind it is the coherent option. It means treating the interface and the backend as two systems that are deployed and maintained separately.

  4. 04

    Not using React

    If there is no JS/TS team, no wish to maintain dependencies and a build, or the interaction is covered by HTML and a little JavaScript, it is not considered. Adding React because it is fashionable brings operating cost without solving anything.

03What we do

React isn't the service: the service is what gets built with it. These are the usual pieces, each one with its scope and its cost.

  1. 01

    Reusable components and the structure of the interface.

    Go to Custom applications
  2. 02

    A design system applied to the application, not loose screens.

    Go to Custom applications
  3. 03

    Integration with the API that serves the data.

    Go to Custom applications
  4. 04

    Component accessibility: focus, keyboard, labels and contrast.

    Go to Custom applications
  5. 05

    JavaScript budget and dependency review.

    Go to Custom applications
  6. 06

    An explicit rendering strategy: SSR, SSG or CSR depending on what each page needs.

    Go to Custom applications
  7. 07

    E2E tests for the critical flows.

    Go to Custom applications
  8. 08

    Deployment and handover with documentation for the component and its operation.

    Go to Custom applications

04Performance and maintenance

Can be measured

  • Weight of the JavaScript shipped per route, and how much is first-party code and how much is dependencies.
  • What loads at the start and what is split out with code splitting.
  • Weight and format of the images the interface serves.
  • Load and visual stability metrics for indexed pages, and interaction time on internal screens.

Can't be promised

  • That React is faster because of its name: performance depends on what is loaded and how it is rendered.
  • That SEO improves just by using SSR or Next.js: crawlability is checked in the served HTML and the real content.
  • A Core Web Vitals result without measuring on the device and network the audience uses.

Maintenance

Update dependencies, review bundle size, maintain the build and the tests. React does not come with a router, rendering or tooling: every added choice is maintained too. The cost is agreed with the project.

Price and timeline

Quoted after diagnosis. It depends on screens, states, API, accessibility, tests and rendering strategy. No figure is published without scope.

See the speed and WPO service

05Proof: stated capability

Declared capability. There are no publishable cases or verified metrics for React interfaces on this project, and evidence per technology is still pending.

What I can explain is the reasoning: how rendering is chosen, how JavaScript is measured and what gets tested for keyboard, focus and zoom before handover.

This page describes when React helps and when it does not; it does not claim specific experience or guarantee performance results.

See the projects

06Frequently asked questions

Does React replace the WordPress theme?

Not by default. A PHP theme with Gutenberg remains the option for a content-first corporate website. React is considered for the interface of an application that consumes APIs, not to change the site front end out of habit.

Is React good for SEO?

It depends on rendering. If the page is served as HTML, with SSR or SSG, the content is crawlable. With pure CSR, the HTML arrives empty and SEO and first load suffer. The strategy is decided per page, not per technology.

What about accessibility?

It is handled at component level: semantic HTML, focus, keyboard, labels and contrast. React does not guarantee it on its own; it needs review and testing, including keyboard and zoom.

What maintenance does it need?

npm dependencies, versions, the build and tests. React is not a complete framework: a router, rendering and tools have to be chosen and maintained. The cost is agreed with the project.

How much does it cost?

Quoted after diagnosis. It depends on screens, states, API, accessibility, tests and maintenance. No rate or delivery time is published for application interfaces.

Can it be used with WordPress?

Yes, as an interface that consumes WordPress data through its API, or with WordPress as a headless CMS. That variant is assessed together with Next.js; this page covers the application interface, not the full headless project.

Next step

Tell us what you need with React.

Send us the context, the URL and what it has to do. We tell you whether it fits and what the next step is.