Web design started in the early 1990s with the use of hypertext documents with static data linked together. The web application era started later on in web history terms and it was helped by the introduction of the forms tag. Nowadays, web applications are replacing desktop applications at an accelerated rate. This is happening because web applications are easier to update, can be used from multiple devices and can be accessed from everywhere.
Creating a new web application
When approaching the creation of a new web application, there is a question that you need to ask. What design pattern to use: A single page application or multi page application? Both design patterns have their pros and cons but each one of them can be seen as ideal depending on the use case. A strong factor in helping to choose which app model is ideal to use for the web application is to follow a content-first approach. With this approach, you will be required to put the application content before everything else and this is ideal since content is the main reason why users will visit a web application. Knowing the content will help to decide what design pattern is ideal to use since we know what data is submitted and received from the server.
MPA advantages over SPA
- MPA does not require heavy client frameworks such as Angular JS, which are required to process data
- When comparing with SPA, MPA is more secure when it comes to cross-site scripting
- Search engine optimisation is easier to implement and can have a better ranking than SPA
- Initial loading time is faster
SPA advantages over MPA
- SPAs are faster since HTML, CSS and scripts are loaded once throughout the lifespan of the application
- Same application can be used as a website and as a hybrid mobile application
- Sending and receiving less data to and from the servers
- Better user experience
- No code is written that compiles pages on the server
To use MPA over SPA or vice versa all depends on the goal of the web application being developed. As previously mentioned, the preferred option is to use a content-first approach. Once you plan all features, data and graphics, you can check if these will fit without overloading in a single page application. If things turn out to be too complex then an alternative approach is multi page application.