Post

@matuzo There are still some interfaces we run into where there are a lot of immediate, app-like interactions that are tough to pull off multi-page.

File management, batch editing, visual or rich text editing, chat/messaging, etc.

Whether or not these are part of a big ol’ SPA or just little islands of interactivity in a multi-page experience depends on what else is going on within the same app 🤷

@matuzo I actually don’t think components are an argument for SPAs. Astro apps show that we can organise code into components that are rendered server-side, but also how we can ship client-side rendered components in a multipage web app.

I’d only recommend a SPA when the app needs state and data to be in sync across pages. This is relatively trivial in a SPA, but incredibly demanding for your infrastructure (e.g. db queries) for a stateless MPA.

@matuzo Apps where: you want the user to be able to switch content in one part of the interface without altering another, or audio/video needs to keep playing while the user navigates, or there are long-running processes that would be interrupted by frequent page transitions (e.g. file uploads).

@matuzo In my opinion, any advantages were purely aesthetic, and I would argue that they no longer exist today.

@matuzo I would add streaming services.
For other use cases, I wouldn’t start with a single-page application.