What is the difference between Single-page Applications and web applications?
Single-page Applications (SPAs) are a subset of web applications. Instead of working by making multiple requests between the client and the server, it provides client-side Model-View-Controller (MVC) architecture, two-way data binding, templates and dependency injection.
When should you not use a SPA?
If the application is simple in nature, you have a limited budget, the initial page load time is a top priority or you are trying to reduce the amount of effort or time needed to debug – Single-page Applications may not be the best solution for you.
What is an example of Multi-page Applications?
MPAs are a simpler option when designing monolithic applications that only have one state. Amazon and eBay are two great examples of MPAs.
Looking to hire?
Join our newsletter
Join thousands of subscribers already getting our original articles about software design and development. You will not receive any spam, just great content once a month.
Using Quill to Build a WYSIWYG HTML Editor [Step-by-Step Tutorial]
Remember how basic the Facebook status update used to be? Now, that same space contains an array of sophisticated text styling options that let users fully express what’s on their minds. This evolution has been driven by rich-text editors like Quill, which...
Tutorial: How to Implement a Micro Front-end Architecture for Your App
Micro frontends first came to light in 2016 as front-end architecture similar to and loosely based on microservices. The architecture was developed in response to common issues with building a growing single-page application, like poor scalability, maintainability and developer experience. Since, they’ve continued to...
Is Tailwind CSS the Future of CSS Frameworks?
There is a divide among the front-end community right now when it comes to Tailwind CSS. From people madly in love with it claiming that “it fixes CSS” to those who discard it as “just abstracted inline styles”, It would seem that no month can...