Pros and Cons of Single Page Applications (SPAs)
A SPA is a web app contained in a single page – where ‘pages’ are nothing but DIVs being shown/hidden based on the state of the app and user navigation.
Single Page Applications heavily use client side scripting to provide rich functionality to the end user.
Gmail is probably the first well known SPA implementation which has been around since 2004.
ASP.NET MVC 4 provides a basic framework for building SPA applications.
Pros:
The big reasons to do SPA are the 3 R's: Reach, Responsive UX and Reducing roundtrip postbacks.
Cons:
Single Page Applications heavily use client side scripting to provide rich functionality to the end user.
Gmail is probably the first well known SPA implementation which has been around since 2004.
ASP.NET MVC 4 provides a basic framework for building SPA applications.
Pros:
The big reasons to do SPA are the 3 R's: Reach, Responsive UX and Reducing roundtrip postbacks.
Cons:
- Navigation – SPA’s by nature break the normal navigation mechanism of the browser. Normally, you click a link, it launches off a request and would update the url on the address bar. The response is then fetched and painted. In an SPA however, a link click is trapped in JS and the state is changed and you show a different div (with a background AJAX request being launched).
- This breaks Back/Forward navigation and since the URL doesn’t change, bookmark-ability is also broken to boot.
- SEO – SEO also breaks because links are associated with JavaScript and most bots cannot follow such links.
A SPA is not a good fit where SEO is important but it can be used for a banking app or an app that shows personalized info where SEO is not required.
Comments
Post a Comment