Next.js application development
Full application work on the App Router — routing, data layer, auth, and the deploy pipeline — built to stay fast and maintainable past launch.
Overview
Most of my work is building and hardening real Next.js applications: the kind with authentication, a database, background work, and a team that has to keep shipping after I leave. I treat the App Router as an application framework, not just a way to render pages — which means being deliberate about where code runs, how data flows, and what happens when something fails.
I come in either at the start of a build or midway through one that has slowed down. In both cases the goal is the same: a codebase where adding the next feature is boring, the production behaviour is predictable, and the performance budget is written down rather than hoped for.
What ships
- App Router architecture: route groups, layouts, loading and error boundaries, parallel and intercepting routes where they earn their place
- Server Components by default, Client Components only at the interaction boundary — with the tree drawn out so the team knows the rule
- Data layer: Server Actions, a caching strategy you can explain, request memoization, and revalidation that matches how the product actually changes
- Database and auth wired end to end — Prisma or Drizzle, PostgreSQL, session or token auth, and the middleware kept lightweight
- Deploy pipeline: preview deploys, environment separation, observability, and error tracking hooked up before launch
- Performance budgets for LCP, INP and TTFB, enforced in CI rather than checked once
A good fit when
- You are starting a new product and want the foundation right the first time
- An existing Next.js app has become slow to change or slow to load
- You are migrating from the Pages Router or from a separate SPA + API
- You need someone who can own the front end and meet the backend halfway
FAQ
- Do you work with an existing backend?
- Yes — often. I am comfortable consuming a REST or GraphQL API your team owns, and equally comfortable building the data layer inside Next.js with Server Actions and a database. The right answer depends on your team shape, not on ideology.
- Can you join a project that is already in progress?
- That is a large share of my work. I start with a short audit — architecture, performance, and the parts of the code the team is nervous about — then propose a sequence of changes that improve things without a rewrite.
- How do you keep the team productive after handover?
- Conventions written down, a component and data-fetching pattern that is consistent across the app, meaningful tests around the risky paths, and a README that explains the decisions rather than just the commands.
Tell me about your product
Share a short brief — problem, timeline, and stack — and I'll reply with a candid view on fit, effort, and the fastest path to a shippable milestone.