From the studio
Web Design and Engineering
Next.js, React, modern CSS, performance, immersive web, frontend architecture.
Latest
Core Web Vitals on Next.js in 2026: how to ship green
Concrete steps to hit Good on LCP under 2.5s, INP under 200ms, and CLS under 0.1 on a Next.js 16 SaaS, plus how to read field data when Lighthouse lies.
Immersive web stack in 2026: Lenis, GSAP, and what to skip
Lenis (3 kB), GSAP free since April 2025, ScrollTrigger for scroll math, and native CSS scroll-driven animations. The 2026 stack we ship in production.
TypeScript strict mode: the 8 settings we never turn off
TypeScript's strict: true flag turns on 8 separate checks. Most codebases keep strict on at the root and quietly disable one or two of them inside a problem file. Here is each of the 8, what it catches in production, and the three flags outside the bundle that we still turn on for every project.
Next.js development agency vs in-house: when each one wins in 2026
A US senior Next.js hire costs $195,000 fully loaded and takes six weeks to find. Agency rates run $60 to $250 per hour. Here is how each one wins.
Next.js Server Actions security: 13 advisories and 2026 fixes
Next.js shipped 13 security advisories in 2026: middleware bypass, cache poisoning, and SSRF. What changed and how to ship Server Actions safely now.
Edge runtime vs Node runtime: Next.js 16 moved the default
Next.js 16 moved middleware to the Node runtime and renamed it proxy.ts. Where Edge still wins on latency, where Node wins on packages and long tasks.
Why we removed Tailwind from production: a CSS-only design system
After years of running Tailwind alongside our own design system, we removed it from production. Here is the architecture that replaced it and what changed.
Modern CSS 2026: cascade layers, container queries, :has()
Cascade layers end specificity wars, container queries replace component media queries, and :has() ships in every major browser. What to adopt in 2026.
Why we still pick Next.js over Astro for most SaaS in 2026
We have shipped both Next.js and Astro this year. For SaaS specifically, Next.js stays our default. Here is the honest tradeoff in 2026.
React Compiler 1.0: when you still need useMemo and useCallback
React Compiler 1.0 (October 2025) auto-memoizes most components. Where useMemo, useCallback, and React.memo still earn their place, and what the compiler skips.
Server Components vs Client Components: the decision tree we follow
The five-step decision tree we apply on every Next.js 16 project to decide when a component stays server-side and when it needs "use client".