Skip to main content
Interface Atlas
Guide

Resumability

A rendering paradigm where the server serializes application state into HTML, allowing the client to become interactive without executing component setup code.

Published

Contents

Definition

A rendering paradigm where the server serializes application state into HTML, allowing the client to become interactive without executing component setup code.

Resumability is a fundamental alternative to Hydration. Instead of sending a static HTML shell and then forcing the browser to replay the application’s startup logic to attach event listeners, a resumable framework pauses execution on the server and serializes all necessary state (including event handlers) directly into the HTML structure.

Why It Matters

Resumability completely eliminates the “hydration tax.” Because the browser does not need to execute a massive JavaScript bundle to figure out what the page is supposed to do, Time to Interactive (TTI) is virtually identical to First Contentful Paint (FCP). The page is interactive the moment the HTML arrives.

Resumability vs. Islands Architecture

  • Islands Architecture: (e.g., Astro) You manually define specific components that need to be hydrated. The rest of the page remains static.
  • Resumability: (e.g., Qwik) The entire application can be dynamic, but the framework’s compiler automatically serializes the state, ensuring that the client only downloads and executes the exact JavaScript required for the specific user interaction they just triggered.