Back to news
Mar 2026•Insight•7 min read
Why we reach for React Server Components carefully
RSC shines for content-heavy and streaming UX, but we define boundaries explicitly for apps that rely heavily on client-only APIs.
Where RSC adds value
For content-rich surfaces and streaming-heavy views, RSC can reduce client JavaScript and improve initial rendering behavior.
In those contexts, the DX and runtime benefits are clear when boundaries are thoughtfully designed.
Where we stay client-first
Apps using complex browser APIs, canvas, map rendering, and realtime interactions still need significant client logic. Forcing RSC everywhere can create unnecessary complexity.
Our rule is simple: choose the architecture that keeps code maintainable and user interactions reliable.