We're working on https://github.com/rails-api to make Rails a great backend for APIs, and specifically Ember. Team is mostly Rails Core members and Ember team members.

The hope is to make it awesome for other JS frameworks too, but we mostly build Ember apps ourself, so you start with what you know...

Huge +1 on rails-api. When used in combination with rabl, it's the most formidable Backend solution there is.

Glad to hear rabl is working well in conjunction with rails-api. Haven't had a chance to try that combination yet, mostly been using rabl alongside Sinatra, Grape and Padrino.

As I said below, if it doesn't, please let us know: I'd consider that a bug.

We actually think that AMS is significantly better, but I'm glad rabl works well for you. :)

Mostly for the gluing and custom node editing, but also I really like keeping my rabl files (presentation) outside of my models

Totally. And there's a reason AMS isn't part of rails-api proper: we want you to pick the tools you want to use. If rails-api (the gem) doesn't work with RABL in some way, please let me know, that's a bug.

You haven't seen the full power of AMS yet, but I have some exciting things planned. :)

You can do both, for example, you can use rails for authentication with traditional views and then use ember for the main single page app. I think this is how square does it.

Also you should look into active model serializers for integrating rails with ember. I think it's yehuda Katz' preferred method for Jason serialization from rails to ember.

> I think it's yehuda Katz' preferred method for Jason serialization from rails to ember.

That is true. AMS + Ember-data = 👍 (I'm now maintaining AMS, but Yehuda and Jose Valim originally wrote it for this purpose.)