Web applications are unwittingly replacing the old desktop applications. They are more convenient to use, they are easy to update, and they are not bound to one device. And even though users are gently moving from browser-based web applications to mobile ones, the demand for complex and refined apps is already huge and is still growing. If you are thinking about creating your own application, you’ve probably heard that there are two main design patterns for web apps: multi-page applications (MPA) and single-page applications (SPA). And, of course, both models have their pros and cons.
Before you start turning your idea into a real application, you have to answer a bunch of important questions. To decide what app model is better for you, you should follow a content-first approach, which emphasizes the importance of putting your application content before everything else. That’s because the content is the main reason why users will or won’t use the application. And this leads us to the most important questions: What content do you want to present? And what content will your users care about the most?
There are many pros and cons of SPA as well as MPA. I hope that the lines below will clear the differences between these two design patterns and bring you closer to the point where you will know what kind of application fits your idea more. And make your idea about your own application come true.
Read also: All you need to know about PWA on iOS
A single-page application is an app that works inside a browser and does not require page reloading during use. You use this type of application every day. These are, for instance: Gmail, Google Maps, Facebook, or GitHub.
Single-page sites help keep the user in one comfortable web space where content is presented to the user in a simple, easy, and workable fashion.
Read also: PWA vs. native App vs. hybrid App – which solution will work best for you?
Pros of the Single-Page Application:
- SPA is fast, as most resources (HTML+CSS+Scripts) are only loaded once throughout the lifespan of the application. Only data is transmitted back and forth.
- The development is simplified and streamlined. There is no need to write code to render pages on the server. It is much easier to get started because you can usually kick off development from a file file://URI, without using any server at all.
- SPAs are easy to debug with Chrome, as you can monitor network operations, investigate page elements and data associated with it.
- It’s easier to make a mobile application because the developer can reuse the same backend code for web applications and native mobile applications.
- SPA can cache any local storage effectively. An application sends only one request, stores all data, then it can use this data and work even offline.
Cons of the Single-Page Application:
UPDATE 27.09.2017: In her comment at Medium, Iris Shaffer correctly pointed out that it can be done on the server side as well. Indeed, it is easier today than it used to be.
- It is slow to download because heavy client frameworks are required to be loaded to the client.
- Compared to the “traditional” application, SPA is less secure. Due to Cross-Site Scripting (XSS), it enables attackers to inject client-side scripts into the web application by other users.
- In this model, back and forward buttons become dysfunctional.
UPDATE 27.09.2017: Nowadays, it’s not an issue anymore.
Read also: How to start working with Protractor
Multiple-page applications work in a “traditional” way. Every change, e.g., displaying the data or submitting data back to the server, requests rendering a new page from the server in the browser. These applications are large, bigger than SPAs, because they need to be. Due to the amount of content, these applications have many levels of UI. Luckily, it’s not a problem anymore. Thanks to AJAX, we don’t have to worry that big and complex applications have to transfer a lot of data between server and browser. This solution improves and allows to refresh only particular parts of the application. On the other hand, it adds more complexity, and it is more difficult to develop than a single-page application.
Pros of the Multiple-Page Application:
- It’s the perfect approach for users who need a visual map of where to go in the application. Solid, few-level menu navigation is an essential part of a traditional multi-page application.
- Very good and easy for proper SEO management. It gives better chances to rank for different keywords since an application can be optimized for one keyword per page.
Cons of the multiple-page application:
- Front-end and back-end development are tightly coupled.
- The development becomes quite complex. The developer needs to use frameworks for both the client and the server side. This results in a longer time of application development.
SPA or MPA?
Before deploying a web application, you need to consider its goal. If you know you need multiple categories (because, for instance, you run an online shop or publish a lot of other content) — use a multi-page site. If you are sure that your site is appropriate for a pure single-page experience — go for it. And if you like SPA but can just barely fit everything into a single page, consider a hybrid site instead. This is another way I haven’t mentioned before. A hybrid application takes what is best in both approaches and tries to minimize the disadvantages. It is, in fact, a single-page application that uses URL anchors as synthetic pages enabling more in-built browser navigation and preference functionality. But this is a topic for another article.
Perhaps in the future everyone will use a single-page application model (including a hybrid app), as it seems to bring a lot of advantages. Many apps on the market are migrating towards this model. However, as some projects simply cannot fit into SPA, the MPA model is still vivid.
Read also: Progressive Web Apps: what is it? Benefits of PWA