There's no standards, but at this point I'd say Flux + React-router are quickly becoming it. react-router is made in the spirit of Ember's which is pretty well liked.
- Flux Architecture Pattern [0]
- React Router [1]
Note that there isn't really a prescribed model in Angular aside from $scope either.
I like react-router that looks quite nice. Flux looks like a description of an idea rather a JavaScript library. Is there a flux store that persists to a REST backend?
A model really isn't part of Angular core since it was split out but something like angular-resource is what I am talking about.
This is certainly the biggest reason. In the future maybe we can use ember-cli and integrate more with them.
Ember does a LOT of what I want recroom to be able to do, but I'm okay using something that works better right now over using bleeding edge Ember stuff that may be more idiomatic.
Of course, as more people contribute to and use recroom we'll evaluate changing out components. If I picked the wrong thing I hope people will correct it and make this thing better ^_^
Yeah you're right. The grunt piece is definitely one that is not set in stone. Ember-CLI is exciting and we've started working closely with the Ember folks to monitor it and see if and when this should become another piece of the recroom puzzle.
Definitely not. Most of the time when I encounter an obvious webpage disguised as a native application, I feel deceived and underwhelmed.
Maybe a little over the top, but honestly it's true. Build a fast, responsive mobile site and be honest about what you're producing. If you want the web and its technologies to win, build and present with the web.
Most of it is custom built rather than using a larger JS framework. We do use a whole lot of libraries for specific tasks though, like moment.js for date formatting, Ace for code editing, Spectrum for the color picker.
ex. https://github.com/Khan/perseus
React's blog usually has some open source projects featured as well - facebook.github.io/react/blog