It can be such a minefield talking about MPAs versus SPAs.
Personally, I’ve found it far too easy to end up in the weeds concerning this subject — inevitably banging ones own subjective drum.
In Jeremy’s post — (response to a question) — about why he seems to advocate the use of multi-page web apps and not single-page ones, I think he articulates his views really well on this prickly subject… without teeth.
For most use cases, a website (or multi-page app if you prefer) is going to provide the most robust experience for the most number of users. That’s because a user’s web browser takes care of most of the heavy lifting.
Why single-page app architecture may be more suitable…
There are some cases where you’d want a state to persist across pages. Let’s say you’re playing a song, or a podcast episode. Ideally you’d want that player to continue seamlessly playing even as the user navigates around the site. In that situation, a single-page app would be a suitable architecture.
Don’t think it’s for free though…
When it comes to front-end development, I’m worried that we’ve reached a state where the more complex over-engineered approach is viewed as the default.
I hope I’m wrong. I hope that other developers will start to consider user experience first and foremost when making architectural decisions.
← Other bookmarks