> If you’re writing an application that will likely only be communicating with an API or back-end data service, where much of the heavy lifting for viewing or m

> If you’re writing an application that will likely only be communicating with an API or back-end data service, where much of the heavy lifting for viewing or manipulating that data will be occurring in the browser, you may find a JavaScript MV* framework useful. This, in my opinion is the most critical point when thinking about which framework you want. Once you know that, for example, you are going to do a lot of heavy UI manipulation and you do want an MV* framework, I think you end up splitting hairs about the differences between the frameworks. Spine or Backbone or Ember or whatever. At the end of the day, those frameworks are just the starting point and with any application of significance, the custom standards you put in place will have a much bigger impact than the framework you start off with.