Developers these days are spoiled with choice when it comes to selecting an MV* framework for structuring and organizing JavaScript web apps.

Backbone, Ember, AngularJS, Spine... the list of new and stable solutions goes on and on, but just how do you decide on which to use in a sea of so many options?

To help solve this problem, we created TodoMVC - a project which offers the same Todo application implemented using MV* concepts in most of the popular JavaScript MV* frameworks of today.

• Backbone.js
• Ember.js
• AngularJS
• Spine
• KnockoutJS (MVVM)
• Dojo
• YUI
• Batman.js
• Closure
• Agility.js
• Knockback.js
• Google Web Toolkit

• jQuery
• Vanilla JS

• Backbone.js + RequireJS
• AngularJS + RequireJS
• KnockoutJS + RequireJS
• CanJS + RequireJS

We also have a number of in-progress applications in Labs:

• React
• Meteor
• Derby
• CanJS
• Kendo UI
• Flight by Twitter
• Maria.js
• cujoJS
• MarionetteJS
• SocketStream + jQuery
• Ext.js
• Sammy.js
• dermis
• Stapes.js
• Epitome
• TroopJS
• soma.js
• DUEL
• Olives
• PlastronJS
• Dijon
• rAppid.js
• Thorax
• KnockoutJS + ClassBindingProvider (using Ryan Niemeyer's Class Binding Provider)
• KnockoutJS + RequireJS (using AMD)
• AngularJS + RequireJS (using AMD)
• CanJS + RequireJS (using AMD)
• AngularJS (optimized)
• Backbone.xmpp
• Dart
• Chaplin + Brunch
• Serenade.js
• TypeScript
• DeftJS
• Aria Templates
• Enyo + Backbone.js
• SAPUI5
• Lavaca + RequireJS (using AMD)

Live demos are available on our website

Click on the button below to view the code in a Web IDE. Feel free to edit the code and then run it all from your browser.

TodoMVC would not be possible without a strong team of contributors helping push the project forward each day. In addition, we have a core project team composed of:

TodoMVC has been called many things including the 'Speed-dating' and 'Rosetta Stone' of MV* frameworks. Whilst we hope that this project is able to offer assistance in deciding what frameworks are worth spending more time looking at, remember that the Todo application offers a limited view of what a framework may be capable of.

It is meant to be used as a gateway to reviewing how a basic application using a framework may be structured and we heavily recommend investing time researching a solution in more depth before opting to use it.

Whilst we enjoy implementing and improving existing Todo apps, we're always interested in speaking to framework authors (and users) wishing to share Todo app implementations in their framework/solution of choice.

Check out our contribution docs for more info.

Everything in this repo is MIT License unless otherwise specified.

MIT © Addy Osmani, Sindre Sorhus, Pascal Hartig, Stephen Sawchuk.