App Router architecture
Server components by default, client components only where interaction genuinely requires them — the smallest JavaScript bundle the feature can be built with.
Available for contract, freelance and full-time engagements
Next.js & React Development
Next.js is the framework I reach for when an application has to be fast, indexable and maintainable at the same time. Static generation and server components mean pages arrive as HTML rather than as a loading spinner — which matters both for users on slow connections and for search engines deciding whether a page is worth ranking.
What this covers
Static generation and rendering strategy
SSG, ISR or SSR chosen per route against how the data actually changes, rather than applying one strategy everywhere.
Technical SEO
Metadata, canonical URLs, structured data, sitemaps and Open Graph images generated from the content layer, so they cannot drift out of sync with the page.
Migration from SPA
Moving client-rendered React applications onto Next.js — the migration this very site went through, from Vite SPA to statically generated App Router.
Tools and technologies
Next.jsReactTypeScriptTailwind CSSVercelPrisma ORMGraphQL
Proof of work
Projects where I have already done this, written up as case studies.
FHRADC Enterprise Management System
Permission-driven ERP covering HR, finance, procurement, approvals, payroll and audit.
Read case study: FHRADC Enterprise Management SystemCodeAtlas
Privacy-first local AI tool that semantically indexes codebases and answers questions about them.
Read case study: CodeAtlasGolden M International
Responsive marketing site for a construction materials supplier, with multi-language navigation.
Read case study: Golden M InternationalQuestions
Why move a React SPA to Next.js?
A client-rendered SPA ships an empty HTML shell and builds the page in the browser. That costs you first-paint performance and gives search engines a page with no content in the initial response. Next.js renders to HTML at build time, so the content is in the document.
Will Next.js improve our search rankings?
It removes technical obstacles — server-rendered content, fast Core Web Vitals, correct metadata and structured data. It does not by itself create something worth ranking for; that comes from having pages that answer real queries. Both matter, and I work on both.
Do you use the App Router or the Pages Router?
App Router for new work, for server components and the metadata API. I can work in the Pages Router on existing codebases where migrating is not currently worth the disruption.
Other services
LET'S TALK SPECIFICS
If next.js & react development is what you need, tell me about the system, the constraints and the timeline.