title: best practices for "data layer" in android client apps
body: <p>Here is one design/ best practices question..</p>
  
  <p>I'm new to android development, and basically new to web/mobile solutions. </p>
  
  <p>So, my question is - what are best practices when organizing structure of android application that get data from the remote server?</p>
  
  <p>Should request to server go into one class that does communication with server (get and post requests), or should I look at my requests as data source, meaning that every data class manages it for itself?</p>
  
  <p>or should I have more levels of abstraction - one level for acquiring data, other for model that uses some interfaces without knowing from what source data come from?</p>
  
  <p>I'm curious how experienced android developers approach to these design issues...</p>