I haven't handled routing yet, a lot of people seem to use https://github.com/flatiron/director https://github.com/flatiron/director, which I would probably do.

I haven't handled routing yet, a lot of people seem to use https://github.com/flatiron/director https://github.com/flatiron/director, which I would probably do. This is the one area where I missed something from Ember. For models, I've just rolled my own so far. I've experimented in one small project with having a global state object that cotnains all application state data, and then just having domain fns that operate on that data. Inspired by the react people's descriptions of "flux" architecture. It felt really nice. When using Ember, I got really confused by Ember's Ember Data vs. Ember Model vs. whatever conversation. Again, I just didn't really know what to do here, and I attribute it to my own shortcomings.