title: Is it wise to build an MVC app around a RESTful API using nothing but HttpClient?
body: <p>My boss wants a full REST API for our new project. But, he also wants a UI for it and our deadline is not very generous. Learning a decent front-end framework (Angular, React, Vue) might prove to take a little too long.</p>
  
  <p>He is asking if we could talk to the REST API using MVC entirely. I explained to him that MVC means the view is tightly coupled to the controller.</p>
  
  <p>He asked why we cannot just build out the REST API fully, and then make an MVC app that uses <code>HttpClient</code> in the controller (or a service class) to hit the API.Is that a bad idea? I told him it seemed like another big layer to maintain and that most people are probably using a nice front-end framework to talk to their back-end.</p>
  
  <p>I also felt like I did not know enough about how other people handle this situation. So those of you that <strong>MUST</strong> have a REST API for all new apps. How do you build your UI for it? We are using Swagger, so generating TypeScript or C# clients is possible if that helps.</p>