This is incredibly cool. The template syntax you have going is awesome. Reminds me of the natural language of haml/ruby with the handy pipe filter stuff of django/jinja. I can't stand mustache and handlebars.

The UI is great, it's responsive, and well thought out.

Also, the data modeling issue is a great selling point. Right now, MOST all applications are the same. Take this data, validate the person sending you the data is correct, validate the data is correct, and store it. Then apply the same methodology to fetching it, modifying it, or deleting it. I've been a django/python guy for years but after recently diving into Rails, I don't think anyone has done this any better. You can very quickly get things moving in CRUD/REST without much code.

That being said, it all comes back to the modeling. Modeling is relatively simple in Rails. The ORM you get with Django far exceeds ActiveRecord in usability but either way, at some point, a developer needs to sit down and define the data modeling. I realize you're marking this to developers (obviously) but I feel like with your cool UI and mongodb backing, you might even be able to expand this to administrators of the service.

Meaning, I can deliver a pre-configured product to my clients but if they want to add some fields to a product that are searchable/sortable/validatable/etc... they won't need to wait for me to do it. They won't need to wait for me to deploy it. I won't need to run a migration script.

Modern REST frameworks typically work based on a separation of a model and a resource. The model handles data storage and representation, and the resource handles serving it up, controlling access, etc... I think we need to couple these together. One unified object. I can create something, like a `Product`, give it some properties, set validations and permissions for those properties, and boom. Done.

Things like this and Meteor are shining examples of the radical change that we need in this current era of development. Yes, you guys will find faults in that statement. The neckbeards will come out and tell me mongodb does not scale, or node.js async development does not make sense. That is not the point. The point is that we're really not making it much easier on ourselves to build the things we want. Right now it makes more sense for me to pay Parse to handle an iOS back-end. Why? Because for the most part building it is a pain in the ass.

It doesn't need to be. I'm excited about Forward, very excited.