carloscortegagna/todomvc

Helping you select an MV* framework - Todo apps for Backbone.js, Ember.js, AngularJS, Spine and many more

TodoMVC

Helping you select an MV* framework

Introduction

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.

Todo apps are included for:

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

Non MV*

• jQuery
• Vanilla JS

RequireJS

• Backbone.js + RequireJS (using AMD)
• Ember.js + RequireJS (using AMD)

Labs

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

• CanJS
• Maria.js
• cujo.js
• Meteor
• SocketStream + jQuery
• Ext.js
• Sammy.js
• JavaScriptMVC
• Stapes.js
• Epitome
• TroopJS
• soma.js
• DUEL
• Fidel
• Olives
• PlastronJS
• Dijon
• rAppid.js
• Broke
• o_O
• Fun
• KnockoutJS + RequireJS (using AMD)
• AngularJS + RequireJS (using AMD)
• AngularJS (optimized)

Live demos

Live demos are available on our website

Screenshot

Team

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:

Addy Osmani - Founder/Lead

Addy is a Developer Platform Engineer at Google who originally created TodoMVC. He oversees the project direction, drives expansion and helps lead core development with Sindre Sorhus (by far our most active contributor!).

Sindre Sorhus - Lead Developer

Sindre is a Web Developer who drives core development, quality control and application design for the project. His contributions have helped us ensure consistency and best practices are enforced wherever possible.

Gianni Chiappetta - Logo designer

Disclaimer

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.

Project Status

TodoMVC 1.0 was just released and includes re-writes of almost all applications, ensuring they follow a consistent set of specifications and are using the latest versions of all libraries and frameworks in use. We've also addressed framework author concerns about routing by adding this to many of the more mainstream applications in the project.

Getting Involved

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.

New Applications

If you have an implementation you would like to show us or a patch you would like to send upstream, please feel free to send through a pull request after:

• Reading our contribution guidelines
• Going through our application specification
• Looking at our most recent reference application

One of us will be happy to review your submission and discuss any changes that may be required before they can be included. Applications will typically land first in Labs, reaching the 'stable' mark once we have verified they meet all of the application specifications referenced above.

Unit Tests

At present, due to the large number of applications in the TodoMVC suite we haven't been mandating that unit tests be written in order for an application to be accepted.

We do however plan on addressing this in a future release as we feel it would both help further ensure consistency and provide developers with a reference for writing tests for each framework.

If you are a library author or contributor wishing to start work on writing tests for an implementation, we'll happily consider including them in the future. This may change based on how we specify unit tests must be structured and so on post 1.0.

A Final Note

Note that due to the current number of MVC/MVVM/MV* frameworks in circulation, it's not always possible to include each one in TodoMVC, but we'll definitely discuss the merits of any framework prior to making a decision :)

For applications that we feel don't quite match the goals of the project, but which we feel still offer value, we're happy to include references to them in our official wiki.

License

The Unlicense (i.e Public Domain)