Next Project Contacts
A laptop open on a dark desk at night, its screen lit with soft blue interface panels, city bokeh blurred behind it.

Frontend

React development built to change.

React work judged on what it costs to change later on: component boundaries, state that stays boring, and a render budget nobody has to guess at.

Contacts Technology map

React is easy to start and expensive to maintain badly. Most of the React work we are called in to rescue is not slow because of React — it is slow because nobody drew a line between what a component owns and what it borrows.

Plain wooden blocks on a dark bench, some assembled into a small frame and two set aside.

How we judge it is going well

  1. Where the boundaries go

    We decide early which components hold state, which only render it, and which are allowed to fetch. That single decision is what keeps a screen understandable after a long line of people have touched it. Everything else — folder shape, naming, which library won this year's argument — is a detail underneath it.

  2. State that stays boring

    Server data belongs in a cache with an explicit invalidation rule. UI state belongs close to the element that owns it. Global state is for the handful of things that genuinely are global: session, theme, feature flags. Projects get into trouble when those three categories are treated as one.

  3. Performance is a budget, not a rescue

    • A measured render budget per screen, checked in CI, not after launch
    • Lists virtualised only when the numbers say so
    • Bundle splits along routes people actually visit
    • Images and fonts handled once, in the layout, not per page

  4. The accessibility floor

    Keyboard reachability, focus order and visible focus are part of the component review, not a later audit. A modal that traps focus correctly costs almost nothing when it is written and a great deal when it is retrofitted.

  5. When React is the wrong answer

    If the page is text and images that change weekly, a React app is overhead you will pay for forever. That work goes to Astro instead. If the product needs server rendering and route-level data, we reach for Next.js. We say which one we would pick before the contract, not after.

    Every component we ship is typed — see TypeScript — and styled through the token layer described under Tailwind CSS. The wider picture is on web development and the rest of the technology map.

Discuss the next step

Tell us what you want to build or improve. We reply with a plan, an indicative budget and a start date.

Contacts Browse the service map