Selecting the correct technology stack can make or break a project. Sometimes, the desire to use the next ‘hot’ technology leads stakeholders (both technical and non-technical) to make unwise decisions in this department.
While SPA frameworks have been around for years, they continue to evolve, with new versions generating buzz within the development community. The above Twitter example shows that, while developing an SPA may sound like an exciting option, it may not be the right one for your project.
In this article we will look at the pros and cons of SPA frameworks, so your team can make the decision based on information – not ego!
The road to Single Page Applications
Before the first SPA framework appeared, the landscape was dominated by Multiple Page Applications (MPAs) built in static HTML and server-side technologies like PHP, ASP, Java, Ruby, and Python. It should be noted that what we consider to be a “normal” website even today, is the same as what we’re calling an MPA.
MPAs work by making multiple requests between the client and the server. As websites have grown in complexity, so have the demands they make on servers. The introduction of AJAX, which allows web pages to be updated without reloading, partly alleviated this issue. It also gave developers a glimpse into how an SPA future might look.
Next came the Knockout.js framework and its introduction of MVVM data binding. Knockout.js simplified the data binding process by creating a separation of concerns between the view and the application’s data. It did this by taking the view model and binding it to the browser’s HTML, so any changes in the browser were automatically tracked and reflected in the view model – and vice versa!
The MPA (traditional web application) legacy
MPAs still form the vast majority of web applications online. While this is partly due to a head start over Single Page Applications, there are many use cases where building an MPA is simply the better option. In fact, many of the web’s most popular websites have opted to remain as MPAs. These include Stack Overflow, Amazon and most WordPress-based sites. MPAs have a long track record and are proven to work great for a variety of applications.
So, how can you decide which option is best for your project? The key to choosing the correct framework lies in understanding your project’s requirements and how they map to your technology needs. I’ve prepared the comparison below to aid in this effort.
MPA Pros & Cons
MPAs are a simpler option when designing monolithic applications with only one state section.
The initial page load is normally faster than the initial page load of an SPA.
Subsequent pages take equally long to load because a request is sent to the server for data and UI rendering.
SEO is easier and more effective as most search engine crawlers were built for MPAs.
Requests are handled by the server and most MPA frameworks present tried and tested security.
Most developers will have MPA experience already.
MPAs are supported by many popular debugging tools included in Integrated Development Environments (IDEs).
Not all code can be re-used for a mobile version of the application which means extra development time.
MPAs are generally cheaper to build because they use more established technologies and there are more developers in the market.
SPA Pros & Cons
Pages load faster when a user navigates within the application which results in a “snappier” user experience after the initial load.
More advanced, richer applications can be built with Single Page Applications
It takes more time to initialize the application as it has to be downloaded to the user’s device. But this can be improved by server-side rendering.
Enterprise apps can be harder to design and maintain as SPAs due to the larger number of files generated as well as the need to maintain two states between the SPA and the RESTful API.
SPAs can drain battery power faster than MPAs, as there is a bigger workload on a device’s browser.
SEO optimization can be less effective with content loaded through AJAX. This is because SEO crawlers mostly rely on stable content within distinct pages. This is rarely an issue as Google now crawls SPAs with high fidelity.
SPA frameworks can be used to develop mobile applications that facilitate code reusability down to the level of UI elements.
Smart developers are excited to work on Single Page Applications since they are new and are likely going to be used even more in the future
This is a relatively young technology but the active community means that many issues associated with SPAs are getting resolved.
Single Page Applications require more effort and knowledge to debug. This is because developers have to use their browser’s development tools rather than IDEs.
SPA code can be hard to trace. Especially when integrating third-party modules and plugins.
Single Page Applications are newer and your development team will need to be familiar with the specific framework and tools (eg: NPM, Webpack, SystemJS, Gulp). These skill requirements can increase the hourly rate of your developer(s).
Single Page Applications are generally more expensive to build because they require developers to know newer technologies. Debugging is slower and harder. There are also fewer 3rd party libraries to use to keep costs down.
Popular Single Page Application frameworks
If you have decided that building an SPA best suits your project, there is still the small matter of selecting an SPA framework. This is a hotly debated topic (I’m not kidding, typing ‘Angular vs React’ is like stepping into a war zone) and one that is beyond the scope of this article.
But I will leave you with a list of the 5 most popular and well-supported options. I suggest you apply the same rigorous analysis we carried out above to select the most appropriate framework for your project.
Improvements in the “snappiness” of an application and a richer, more immersive user experience are often cited as key reasons to go with Single Page Applications. The recent SPA redesigns of streaming music site Pandora and Google’s Gmail platform are great examples of this in practice. But, as we noted with Twitter, these benefits are not guaranteed. It is vital to take a considered, project-by-project approach to choosing your technology stack. Not doing so can result in emotions or social pressures hijacking the decision process.
The risks fall into a few broad categories: talent skills, talent cost, stability, SEO, and security. These shortcomings are not unusual for a new technology and are being fixed at pace thanks to an active and motivated community. They are, however, still factors that need to be considered in your decision-making process. If you find you are struggling to find the right talent for your project why not get in touch. Sourcing great talent is what we do best at Scalable Path.