All posts

    WEB DEVELOPMENT

    The End of the Client-Side Router

    2 MIN READ

    How modern full-stack web frameworks are moving routing logic back to the server for performance.

    What the single-page app traded away

    Client-side routing made web apps feel like desktop software, because moving between pages no longer meant a full reload. The cost arrived at the start of the visit. Browsers download a large JavaScript bundle, run it, then fetch the data, often showing an empty page or a spinner along the way.

    Crawlers can be affected too. Many AI crawlers and simple bots do not run JavaScript, so a client-only site can look like an empty page to them however good it looks in a browser.

    Routing moves back to the server

    Modern full-stack frameworks start with server-rendered HTML for each route, then add JavaScript only where the page needs interaction. Data is loaded on the server next to the route that needs it, which removes much of the client-side fetching and many of the loading states that came with it. Navigations can still feel instant, because the framework fetches just what changed and updates the page without a full reload.

    You do not always need a rewrite

    Moving frameworks is expensive, and it is not the only option. Prerendering can generate static HTML for each public route during the build, while the client application takes over in the browser. For a marketing site or a blog, this delivers most of the search and speed benefit with far less change. We used this approach on this site.

    When the client router still wins

    A dashboard behind a login has no need for search visibility, and its users return often enough for a cached bundle to make sense. Highly interactive tools such as editors and design canvases are also natural fits for rich client code.

    The useful question is not which approach is modern, but what each route needs. Public content should be readable as HTML. Private and highly interactive areas can lean on the client. Most real products are a mix of both, and the best frameworks now let you choose route by route.