title: Queuing/saving retrofit requests and send them later when there is poor/no internet connection
body: <p>I have my android application which is not build to work offline, so it is reliant on network connection/data.</p>
  
  <p>App makes a lot of network calls updating the api with new set of data. </p>
  
  <p>I am making changes in it to make it work offline. </p>
  
  <p>Approach I am thinking I will create a Room data base in which I will save the retrofit requests and when there is connection I will pull them from the data base and send it to the api.</p>
  
  <p>does that sound right?
  Is there any other better approach, where I can save requests when there is no connection and when there is connection send those saved requests to the server.</p>
  
  <p>Also can we save requests in Room database</p>
  
  <p>I am not intending on doing database synchronisation with BE(API) and BE(API) deals with requests.</p>
  
  <p>your suggestions are valuable</p>
  
  <p>Thanks
  R</p>