title: Thin or thick REST-client?
body: <p>We have mobile application which takes data from server (REST API)</p>
  
  <p>There are two methods:</p>
  
  <ul>
  <li>/v1/movies (returns movies: id, title, image_url ...)</li>
  <li>/v1/likes (returns movies id that user likes)</li>
  </ul>
  
  <p>Mobile application has a view "My likes" which contains movies that user likes, and this view must also contain necessary metadata (id, title, image_url ...) </p>
  
  <p>I see a few solutions:</p>
  
  <ol>
  <li>Return more info about movies in the "/likes/" method</li>
  <li>Create new method "/movies/likes/"</li>
  <li>Mobile app should make 2 requests. </li>
  </ol>
  
  <p>I know, this is choice between flexibility and speed.
  Where is the border when application becomes thin client instead of thick?</p>