Next.js — the React framework I ship on

Why I use it

Client-only React makes you choose between a good developer experience and a page a crawler can actually read. Next.js removes the choice: Server Components fetch data where the data lives, static rendering turns pages into plain HTML at build time, and the metadata API keeps titles, canonicals and Open Graph tags next to the pages they describe instead of in a separate head-management layer.

What I've built with it

• This site: statically rendered App Router pages, generateStaticParams for every project and stack page, and JSON-LD structured data on each one
• generateMetadata for per-page titles, descriptions, canonicals and Open Graph images
• Server Components and Server Actions to keep data fetching and mutations off the client
• Route handlers where an app needs its own small API rather than a separate service
• Sitemap and robots generated from the same data the pages are built from, so a new page can't go unlisted

Alongside

Rest of the stack

• React.jsComponent-driven web UIs
• ElectronDesktop for macOS, Windows & Linux
• React NativeOne codebase, iOS + Android
• Node.jsAPIs, services & tooling
• ExpoBuild, OTA update & ship RN
• TypeScriptStrict types across every layer
• GraphQLTyped APIs, one query per screen
• FirebaseAuth, Firestore & push
• SupabasePostgres, auth & storage
• DockerReproducible builds & environments