This means, among other things, you don't need server-side URL routing or templates. (You need routing for the REST layer, but that can usually be dynamically generated.)
It's just a much stricter separation: the client deals with view logic and HTML and all that, the server deals with pure business logic behind defined interfaces and data formats.
There is also imdbapi.com which is awesome when it works, but it tends to die a lot.
I find it interesting that you prefer the broader "aggregate of the internet" ratings, rather than ratings based on your friends. The longer we run the site, the more we find it's a bit polarising. Some people like the average of the internet, some people like what's essentially a systematic word of mouth setup.
Not sure if it's just me, but when touching the menu controller on the top left, the dom slide over to reveal... nothing. Also, general weirdness using the gear button to change selection between all/enqueues only/ratings only/reviews only. Selecting something other than all does nothing and doesn't persist.
I'm on Android 2.3.3. My Touch 4g slide. Stock browser.
My only thought is title-bait. This is a usability article, with almost nothing to do with AngularJS. But hey, I guess it worked.
Have you considered:
a) scrobbling a la Last.fm or b) turning the collection of user preferences into a game or a quiz of some kind?
Good luck!
