Single-page applications: when they make sense

A single-page application (SPA) updates parts of the screen without loading a whole new document for every action. It is an application architecture, rather than simply a website with one long page.

Where it can help

Interfaces with repeated actions, such as filtering, editing records or using a dashboard, can keep the context of a task while updating the content.

What needs attention

The initial load, loading indicators and error handling still need careful work. If a request fails, people need to know what happened and whether their changes were saved.

Navigation and accessibility

Back buttons, direct links and focus after a screen change need testing. Updating content dynamically does not automatically make these interactions work well.

A campaign does not necessarily need a SPA

A seasonal promotion or service page may work well as a regular static page. Choose a SPA because its interactions need it.

Describe the steps a visitor needs to take before choosing the technology.

Choose the technology around the task

Describe an everyday task, such as finding a record, editing its details and saving the changes. How often is it repeated? What information needs to stay on screen? These questions help us choose an appropriate structure when developing a custom web application.

Further reading: MDN: Single-page applications.