title: How should a React app (or any SPA) interact with a HATEOAS back-end?
body: <p>The basic question is if there should be one HATEOAS entry point per page or one entry point for the entire app?</p>
  <p>Most examples I have seen implement a single page with a HATEOAS backend, e.g. a list that is paginated using <code>prev</code> and <code>next</code> links. But what happens when the app navigates to a different page that has completely different capabilities and needs a different entry point? How does one organize such an app?</p>
  <p><strong>Concrete example</strong>: We have an app with tab navigation. The home tab shows a product catalog so the entry point is <code>/products</code> which returns page 1 of products along with pagination links. However, now I click on the orders tab which must show a list of past orders. This page needs a completely different entry point <code>/orders</code> which the home tab knows nothing about. In fact, user can directly navigate to the orders tab using a deep link.</p>
  <p>How to think about this problem? Are there any examples illustrating an approach?</p>