On point 1: "AngularJS is, for lack of a better term, an MVC framework."<p>It is not an MVC framework. The angular team even describes it as an MVW framework (the W stands for Whatever).<p>Angular on its own does not provide enough structure to work on large projects. It requires a better structure than using directories called 'controllers', 'services' and 'directives'. These are just angular concepts that do not translate well into understanding of what functionality should go in each directory. If you've worked on a larger project, you may have already seen this problem.<p>Angular documentation is not very helpful in pushing this point to the developer, however. It recommends[1] the use of 'services' as the place to do all business logic, which causes many projects to put most of the code in the 'services' directory.<p>To work on larger projects, you should create the MVC structure to fill in the gaps that angular does not provide. Creating top level folders such as: Models, View Controllers, Controllers, Endpoints (server communication). And using services, not as a top level folder, but as a way to instantiate components.<p>[1] <a href="https://docs.angularjs.org/guide/concepts" rel="nofollow">https://docs.angularjs.org/guide/concepts</a>