title: Project organization and naming conventions
body: <p>This is somewhat a follow-up to <a href="https://stackoverflow.com/questions/25005897/repeating-module-name-for-each-module-component">Repeating module name for each module component</a> question.</p>
  
  <p>We've decided to follow the suggested in <a href="https://docs.google.com/document/d/1XXMvReO8-Awi1EZXAXS4PzDzdNvV6pGcuaF4Q9821Es/pub" rel="nofollow noreferrer">Best Practice Recommendations for Angular App Structure</a> blog post angular project organization and naming conventions while building a small internal application for measuring connection quality. </p>
  
  <p>And this is what we've got at the moment:</p>
  
  <pre><code>$ tree -L 1
  .
  ├── app-config-service.js
  ├── app-config-service_test.js
  ├── app-connection-service.js
  ├── app-connection-service_test.js
  ├── app-controller.js
  ├── app-controller_test.js
  ├── app-countdown-directive.js
  ├── app-countdown-directive_test.js
  ├── app-footer-directive.js
  ├── app-footer-directive_test.js
  ├── app-footer-service.js
  ├── app-footer-service_test.js
  ├── app-math-service.js
  ├── app-math-service_test.js
  ├── app-stats-directive.js
  ├── app-stats-directive_test.js
  ├── app-status-directive.js
  ├── app-status-directive_test.js
  ├── app-status-service.js
  ├── app-status-service_test.js
  ├── app-time-directive.js
  ├── app-time-directive_test.js
  ├── app.css
  ├── app.js
  ├── bower_components
  ├── config.json
  ├── countdown.html
  ├── footer.html
  ├── img
  ├── index.html
  ├── ping
  ├── stats.html
  └── status.html
  </code></pre>
  
  <p>As you can see, there are several directives, services, partials, single controller, module declaration file and couple config and app-specific unrelated to the topic files. This really becomes a mess of files and is not quite readable and easy to work with.</p>
  
  <p>This is probably because <em>we have only one single module</em> and keep everything inside it.</p>
  
  <p>Is it okay to use the good old component-oriented approach and have special directories for <code>services</code>, <code>controllers</code>, <code>directives</code> and <code>partials</code> for such a simple app? Does this mean that the new "Organized by feature" approach work only for non-trivial huge applications?</p>