How I Decide which Web Front-End Framework to Use

It almost seems like every other week there is a new MVC web front-end framework. The front-end dev community is incredibly vibrant and projects are moving rapidly; introducing new features all the time, changing development paradigms and experimenting with new ES6 language features. You probably have heard of Backbone, Marionette, React, Flux, Angular, Web Components, Ionic, Cordova, WinJS, Ember and tons of other frameworks. It’s overwhelming trying to decide which one is the right one and there’s often a fear over choosing the wrong framework. Let me show you how I decide which web front-end framework to use.

If I want to build a simple MVC app with a framework I could learn in under 30 minutes, I would go with Backbone.

I am not expecting everyone who reads this article to agree with my decision making process. In fact, I would like to challenge you to name me alternatives following the same type of thought process as above. For example; if you have an alternative to Topcoat, simply tweet @ramisayar and I will include it.