Skip to content
Book a free 30-minute call with an engineer

React development

Our default for dashboards and complex web UIs.

TypeScriptTanStack QueryZustandRedux ToolkitReact Hook FormZodTailwind CSSStorybookVitestPlaywright

Frontend

Building with React

We use React when a web app has a lot going on in the interface: live dashboards, multi-step forms, editors, admin panels that keep growing. You build a component once (a table, a date picker, a permissions banner) and use it on every screen. On a product that's two years old, that's the difference between adding a page in a day and adding it in a week.

Our React projects run on TypeScript from the first commit, with TanStack Query for server data and a small amount of global state, usually Zustand. We write Playwright tests for the flows that make money (sign-up, checkout, the main workflow). We also take on existing codebases, including migrations off jQuery, AngularJS or old class components, and we can add React developers to a team that already has one.

InvoiceList.tsxTSX
1export function InvoiceList({ invoices }: Props) {​
2 const [filter, setFilter] = useState<Status>("open");​
3 const visible = useMemo(​
4 () => invoices.filter((i) => i.status === filter),​
5 [invoices, filter],​
6 );​
7​
8 return (​
9 <section>​
10 <StatusTabs value={filter} onChange={setFilter} />​
11 {visible.map((inv) => (​
12 <InvoiceRow key={inv.id} invoice={inv} />​
13 ))}​
14 </section>​
15 );​
16}​

The kind of React code our team writes every week.

What we build with React

  1. 01

    Custom React web applications

    Apps built around how your team actually works. Routing, forms, auth and role-based access are planned before the first screen, not bolted on later.

  2. 02

    SaaS dashboards & admin panels

    Tables, charts, filters and live updates. We virtualise long lists so a 10,000-row table still scrolls smoothly.

  3. 03

    Design systems & component libraries

    A shared component library in Storybook, themed to your brand, so designers and developers are looking at the same buttons.

  4. 04

    Legacy front-end migration

    Moving jQuery, AngularJS or class-based React to hooks and TypeScript one screen at a time. No six-month rewrite with nothing shipped.

  5. 05

    Performance work

    We profile first, then fix: code splitting, removing heavy dependencies, memoising the components that actually re-render too often.

  6. 06

    Dedicated React developers

    Senior engineers who work in your repo, follow your conventions and open their first pull request in week one.

Why teams pick React

01

Components you reuse

The second feature is cheaper than the first because most of the pieces already exist.

02

A deep library ecosystem

Forms, data fetching, charts and testing are solved problems. We spend your budget on your product logic.

03

Easy to hire for

React is the most common UI library around, so your codebase won't depend on a niche skill set.

04

Carries over to mobile

React Native uses the same mental model, so web and mobile teams can share patterns and some code.

Good fits

  • SaaS product front ends
  • Internal tools and admin portals
  • Analytics dashboards
  • Customer self-service portals
  • Collaborative editors

Where we use it

React questions

Should I use React or Next.js for my project?

Next.js is a framework built on React, so it's less of an either/or. If you need SEO or a public marketing site in the same codebase, we'd use Next.js. If the whole app sits behind a login, plain React with Vite is simpler and has fewer moving parts. We'll tell you which after a look at your requirements.

Can you take over an existing React codebase?

Yes, and we do it often. We spend the first week or so on an audit (architecture, dependencies, test coverage, bundle size) and send you a prioritised list of what to fix. Then we keep shipping features while working through that list, so your roadmap doesn't stop.

How do you keep a large React app maintainable?

Strict TypeScript, folders organised by feature instead of by file type, one shared component library, and TanStack Query for anything that comes from the server. Most messy React apps we inherit got that way through ad-hoc global state, so we keep it small on purpose. Linting and code review keep everyone on the same conventions.

How quickly can React developers start?

Usually one to two weeks after we agree on scope. They join your GitHub, Jira and Slack and work in your sprints. If you'd rather hand over the whole project, we run it with our own project manager instead.

Pairs well with