title: MVC vs Web API for Multi Page App. Is The Future Web API?
body: <p>I'm starting a new project in super early story phase and I'm a little unsure of what design pattern to use. The app is a reporting app that will allow users to design reports and download them. The app will basically be a wizard style multi page data selector.I'd like to offer the functionality to build these reports from a desktop app too. </p>
  
  <p>Considering the advances in Web API over the past few years, would it be crazy to not use it over MVC? </p>
  
  <p>I've been out of the development game for a bit and it seems that Web API and an angular or other js front-end is the route of choice for new application developers looking to focus on server side business logic along with as many consuming front-ends as possible. There's very little data persistence in this app apart from settings etc. </p>
  
  <p>So am I right to go the web API route? Would this be a good example of when NOT to use MVC? Or I there a middle ground that uses both that's universally understood as being a smart design choice? </p>