I’ve always been under the impression that the use case for AngularJS is applications, and by definition it is not intended for anything where SEO is a concern (e.g. 99.9% of AngualrJS apps should be post-login). Is this not the case? What are you doing with Angular that SEO is enough of a concern to try to work around it, but not enough of a concern not to use Angular?
Full disclosure, I’ve never used Angular but it’s next on my list of things to learn.
I agree with your point regarding applications being dynamic and SEO only for the content heavy stuff. My site is a mix of both where the content is sprinkled with pieces of data that is dynamic.
Although the learning curve was steep and painful but AngularJS saved me from the terrible spaghetti soup of javascript + jQuery. The UI I work on is a bit complex and AngularJS makes it a piece of cake to keep it all-together. Code reuse and stability is awesome. But on the downside I still get caught off guard by "$apply already in progress" and despite all the PhantomJS trickery I am yet to recover from the SEO mess that migrating to AngularJS created for me. Overall the benefits far outweigh the cons though. It was only due to AngularJS that I could add multi-currency support on my site in less than half a day.