What is the “SPA Tax” or better put – the extra cost of building a Single Page Application?
The “SPA Tax” it is a phrase I use to sum up the following points about the comparison of building a normal MVC or ASP.Net web application versus a SPA:
- Currently (2013) it is more expensive to build a SPA
- There is not (currently) a large cohesive body of knowledge on Single Page Application development
- The SEO story is still developing
Some reasons why it is more expensive to build a SPA vs. a normal MVC application as of 2013:
- Development tools are not yet on par with normal MVC application development (time added, so more labor cost)
Lack of a large cohesive Body of Knowledge on Single Page Application development:
- Single Page Applications use technologies and techniques that have been around for a while – some foundation body of knowledge does exist but more as individual components (sort of like learning data structures in computer science – that is good thing, but alone isn’t enough to learn how to write a large business application). Makes me wonder … who, where and how can the existing foundation knowledge be better aggregated and shared (as being related to SPA development)?
- There are still relatively few Single Page Applications in the wild – which means there are a lot fewer web developers that have experience writing a SPA which means there are less web developers sharing their tips and tricks about SPA development.
Currently (2013) the SEO story for Single Page Applications leaves a lot to be desired:
Even with the “SPA Tax” it may be worth writing your web application as a Single Page Application … you just need to be aware of some of the challenges before assuming its just another web application technology that every site should use.
Any thoughts or suggestions?