| I used AngularJS + Express for a reasonably sized custom news app for a client. It does everything form payments, to security, ya know, all the shebang. I agree with is the first but only if you're still in the days of SEO trolling. Frankly it's just not as important if you're doing your other marketing aspects right. For #2, I think there are plenty of ways to build in analytics. We use angularlytics and it works pretty well. Took me like 5 minutes to setup. #3 - Yeoman. Generator Angular. Here's how I do it: 1. Make a client dir, and yeoman up your project with generator angular.
2. Make a server dir and setup an express server.
3. Grunt serve your client dir
4. Make it so express watches your .tmp and app folders for local dev
5. Run your express server
6. When your ready to serve it, Grunt build to a dist folder in your server folder
7. For production, have express serve the dist folder Yeah kind of dirty (since you're running two local servers for dev), but hell, it's fast as can be to setup and a pleasure. #4 Tests? If you're doing tests of any sort, they're bound to slow you down to an extent. #5 Isn't this applicable to all web apps? Mistakes and mismanagement of loading resources is a problem for anything. Sure it has it's problems, but there's just far too much productivity to be gained from using it. For example, Ajax animations are beyond time saving. The real problem with angular is the terrible docs ;) |