What I deliver in React and Next.js
- Business application interfaces: dense tables, filters, rule-driven forms
- Server-rendered sites, when search visibility matters
- Authenticated customer portals, with role management
- Dashboards and data visualisation screens
- Taking over or rebuilding an existing front end, without rewriting everything at once
- A component library reused across screens
What I look at in a front end built to last
Front ends age badly for repetitive reasons: global state that becomes unreadable, a rendering mode chosen once and never revisited, page weight that drifts with every addition. Those are the points I address first, before any styling.
- Component boundaries, with a clear split between display and logic
- State management chosen for the actual need, not out of habit
- Rendering mode decided screen by screen: server, static or client
- Bundle size monitored, images and fonts included
- Keyboard navigation and screen reader support
- Tests on the journeys that are expensive to break
Interfaces delivered
Among the eleven documented projects, several rest on this front-end work: a dating platform with profiles and messaging, an online store with a filterable catalogue, and a project management tool combining a Kanban board with a timeline.
See the eleven documented projects
Frequently asked questions
React or Next.js for my project?
Next.js as soon as search visibility or initial load time matters, which means anything public facing. React on its own is enough for an application behind authentication, where SEO plays no part.
Can you take over an existing front end?
Yes, and it is a common request. We start with a review of the code and its dependencies, then move forward in batches, keeping the application shippable at every step.
Do you work with a designer?
I can start from a Figma mock-up or from a plain brief. Without a mock-up I build on a sober, readable base rather than improvising a visual identity.