[hpvic03]

That's a valid complaint. I wrote it with a Rails backend because that's a pretty popular backend choice for Ember, and they work together well.

Perhaps I can just extract out the Ember portion -- It should still be applicable regardless of the backend.

[Nemcue]

Do you even /need/ a backend though?

It would be much simpler if you keep it entirely client side, using something like Pretender (https://github.com/trek/pretender).

[hpvic03]

To persist data you'll want a backend. That's a fairly important piece of any application which is why I included it in the tutorial. You could ignore the Rails parts of the tutorial and create your own backend.

[pyre]

Persist across clients, maybe, but it's also possible to use localStorage to persist data on a single client.

[TheBrockEllis]

You could also use something like Firebase as a datastore that could persist across multiple clients but also be implemented in javascript.

[endemic]

Maybe stub out the backend with an Express app? Express seems simple enough that even if you're not familiar with it, you can still understand what it's trying to do.

[TheBrockEllis]

And you'd keep most of the code in javascript so new comers wouldn't get "culture shock" by having to learn completely new syntax. +1

[wasd]

Would you consider Parse/Firebase?