title: Is AngularJS just for single-page applications (SPAs)?
body: <p>We are looking at options to build the front end of an application we are creating and are trying to evaluate a tool that will work for us and give us the best platform to move forward.</p>
  
  <p>This is a <a href="http://en.wikipedia.org/wiki/Node.js">Node.js</a> project. Our initial plan was to use Express and go down that route, but we decided that before we kick off this stage it might be best to review what is out there. Our application has several areas which we don't believe fit the single-page model in that they are related from an application perspective, but not from a view one.</p>
  
  <p>We have seen a few of the frameworks we could use to build out the client like <a href="https://en.wikipedia.org/wiki/Backbone.js">Backbone.js</a>, <a href="https://en.wikipedia.org/wiki/Meteor_%28web_framework%29">Meteor</a>, etc. and also AngularJS.</p>
  
  <p>This may be a fairly obvious question, but we cannot seem to decipher if AngularJS is purely for single-page application or it can be used for multi-page applications like Express for instance.</p>
  
  <hr/>
  
  <p><strong>UPDATE 17 July 2013</strong>
  Just to keep people in the loop, I will be updating this question as we go through the process. We are going to build everything together for now, and we will see how well that performs. We have reached out to a few people who are more qualified with AngularJS than us and posed the question regarding splitting up larger applications that share context, but may be too large working on a single page.</p>
  
  <p>The consensus was that we could serve multiple static pages and create AngularJS applications that work with only those pages, effectively creating a collection of SPA and linking those applications together using standard linking. Now our use case is very specific as our solution has several applications, and as I said we are going to try the single code base first and optimise from there.</p>
  
  <p><strong>UPDATE 18 June 2016</strong> The project fell of a cliff, so we never got round to getting too much done.  We have picked it up again recently, but are no longer using angular and are using React instead.  We are still using the architecture outlined in the previous update, where we use express and self contain apps, so for example, we have a <code>/chat</code> route in express that serves up our React chat app, we have another route <code>/projects</code> that serves up the projects app and so on. The way we are kinda looking at it is each app is an aggregate root in terms of its feature set, it needs to be able to standalone for it to be considered an app in itself.  Technically, all the information is out there, its just basic express and whatever flavour of client side app building goodness you want to use.</p>