Technology
Next.js
Next.js is a React framework for full-stack web applications: pages render on the server, data loads next to the interface, and one codebase serves both. I use it for product interfaces, admin panels and multilingual sites, including this one
- Type
- Technology
- Official site
- nextjs.org
- In my work
- Projects 1 · Tools 1 · Services 3
- Published
Where I use it
QRuma: party games on one big screen with phones as gamepads
QRuma runs party games on one big screen. Players scan a QR code and their phones become gamepads, with nothing to install. It grew out of VibeCatter
ToolsQuiz Pack Builder: your own questions for Quiz Battle
Write your own question packs for Quiz Battle and play them on a big screen while players answer from their phones. Use cases, steps and limits
ServicesFrom idea to a working MVP
MVP development for startups: scope, UX, design, frontend, backend, AI and launch, by one senior engineer who has been a founder and a CTO
ServicesA fractional CTO for your startup
Fractional CTO for startups: architecture, team, code review and delivery, from a CTO who also builds. Hours a week, part-time or full-time
ServicesAI agents and LLM apps that work in production
AI agent and LLM development: agents, chatbots on your data, AI features, voice and video pipelines built into a working product, not a demo
What is Next.js and what do I build with it?
Most of my web products start on Next.js. It lets one engineer ship the interface, the server logic and the search-friendly pages of a product without stitching three projects together
Key facts
How I use Next.js
- This site. vibecatter.com runs on Next.js: server-rendered pages in four languages, its own CMS with drafts and publishing, structured data and an admin panel.
- A real-time game platform. The site, the big-screen game view and the phone controllers of my multiplayer platform were built with Next.js, React and TypeScript; the game server itself is a separate Node.js process. Read the case study.
- MVPs. For a new product Next.js covers the marketing pages, sign-in, the dashboard and the API in one codebase, so the first version reaches users sooner. See MVP development.
When I choose Next.js and its limits
I choose Next.js when a product needs pages that search engines can read, an app-like interface and a server in one place. Server rendering keeps the first screen fast, and the same code runs the API.
It is not the tool for everything. A long-running real-time server, such as a game loop, lives better in its own Node.js process next to Next.js. A static landing page does not need a framework at all. And the framework moves fast, so I keep each project on a current, supported version.
Used together with
Sources
- Next.js Documentation — Vercel ·
