For devs shipping a Next.js + Postgres app: auth, billing, and a fast launch end to end.
Reach for this when you're building a real Next.js + Supabase/Postgres product and need it production-ready, not just running locally. It carries you from data model and API to OAuth login, Stripe subscriptions, and a fast, Core-Web-Vitals-clean launch - so the full path from schema to shipped feature is covered by one coherent stack instead of stitched-together advice.
Click to play with sound.
Arranged in the author's recommended order. Walk through them in sequence, or open any one on its own.
Builds and reviews Next.js App Router code – server/client component boundaries, data fetching, caching and revalidation choices, streaming with Suspense, and Server Action mutations – and delivers routes where every dynamic-vs-cached decision is explicit.
Designs GraphQL schemas and resolvers that scale – domain-modeled types, Relay pagination, DataLoader batching to kill N+1, mutation payloads with typed user errors, and depth/complexity limits that stop abusive queries.
Designs normalized, constrained, migration-friendly relational schemas – entity modeling, key and type selection, indexes derived from real query patterns, and safe forward/rollback migrations.
Implements OAuth 2.0 and OpenID Connect correctly – authorization code with PKCE, client credentials for machine-to-machine, state and nonce, exact redirect URI matching, safe token storage, refresh rotation with reuse detection, scopes.
Implements Stripe payments, subscriptions, and webhooks so billing state stays correct – Checkout Sessions, signature-verified idempotent webhook handlers, dunning, and SCA handling.
Builds secure Supabase apps – Row Level Security policies as the authorization layer, schema design against auth.users, Edge Functions for service-role work, realtime subscriptions, and versioned migrations.
Diagnoses and fixes Core Web Vitals – LCP, INP, and CLS – through an ordered audit procedure with concrete code-level changes for images, fonts, JavaScript, and third-party scripts.
Designs REST API surfaces – resource naming, HTTP method and status-code semantics, error shapes, pagination, and filtering – and delivers an endpoint spec a consumer can build against without asking questions.