Building seamless user experiences often involves ensuring that users can navigate within an application without losing their progress or state. In Vue.js applications, this is particularly relevant w...

Native CSS transitions have quietly killed the strongest argument for client-side routing. Yet people keep building terrible apps instead of performant websites.

Single Page Applications (SPAs) have become the go-to architecture for modern web development. By enabling dynamic content loading without refreshing the page, SPAs offer a smooth and seamless user experience that feels more like a native app. However, while SPAs provide impressive usability bene…

Building a SPA (Single-page Application) is a complex puzzle: a JavaScript framework that draws the view, an API serving JSON, and 2 independent…

We spent a decade rebuilding the browser by hijacking routing, manually syncing state, rebuilding forms and transitions in JavaScript to match native app expectations. Now the browser has caught up. It's time to stop the hacks and build on the web again, but properly.

For years, Single Page Applications (SPAs) built with frameworks like React have dominated the web development landscape. They promised fluid transitions, dynamic interfaces, and app-like experiences. But as performance bottlenecks, accessibility challenges, and SEO limitations become more appare…

Some teams force-reload their single-page web apps (SPAs) every few hours just to clear the memory the app leaked. A Playwright soak test finds the leak instead.

Single Page Applications, once a solution for slow browsers, are now a performance bottleneck due to multiple HTTP round-trips.

Buried at the end of this year's installment of my semi-annual series on network and device reality is a mystery: multiple, independent data sets from the Web Performance community indicate sites built as Single-Page Applications ("SPAs") receive, on average, only one (1) "soft navigation" for every

Reports of SPA's death are greatly exaggerated.