EngineeringJanuary 8, 2026·9 min read
Why we chose Next.js for a canvas-heavy application
The architectural decisions behind SketchPad's tech stack and how we use server-side rendering, edge functions, and client-only components together.
AK
Alex Kim
SketchPad editorial team
Marketing and product in one stack
We needed a stack that could serve fast landing pages, authenticated app flows, and highly interactive canvas surfaces without forcing separate deployment systems. Next.js gave us a workable center of gravity.
Choose client rendering intentionally
The canvas itself is unapologetically client-heavy, but the surrounding shell, navigation, and content routes still benefit from server rendering and route-level metadata. That separation improved both performance and SEO.