React & TypeScript Engineering

Back-office applications, B2B portals, operator consoles and management dashboards. We start from the work people do: which decisions they make, which data they need at that moment, which mistakes are expensive. Then we design screens, states and validation around those tasks, including the unglamorous parts: large tables, bulk actions, drafts, error recovery and audit views.

The API is the contract between the two halves. We define it explicitly with OpenAPI, generate typed clients so that a backend change breaks the build instead of production, and agree on error semantics, pagination and validation once. Authentication follows current practice for browser applications: OpenID Connect with a backend-for-frontend where appropriate, so tokens do not sit in browser storage, and authorization enforced on the server.

Clear module boundaries, server state handled by a dedicated library instead of hand-written caching, local state kept local, and a structure that several developers can work in without conflicts. We avoid complexity that the application does not need, such as micro-frontends for a single team.

We implement design systems as reusable, documented components with design tokens, so new screens are consistent by default. Accessibility follows WCAG: keyboard navigation, focus management, contrast and screen-reader semantics, which also matter for public-sector and regulated clients. Performance means small bundles, fast first render and responsive interaction on the hardware your users actually have.

Unit tests with Vitest for logic, component tests for behaviour, end-to-end tests with Playwright for the critical journeys, and automated accessibility checks in the pipeline. Tests run on every change, so the team can refactor with confidence.