title: Internal storage in non-context area
body: <p>I think it's just a basic question but I used to face the problem from different view. It concerns internal storage or any other method of saving data under android dev. </p>
  
  <p>As far I used to dance with qt cpp/c#/dx9 gaming/etc, but what hit me at android development is that context and disinformation. As usual I wanted to decouple the code a bit, this time I decided to swap fragments in one activity, which got me pain in the ass in form of back button control.</p>
  
  <p>Then I thought to myself, let the model control data retrival and save (viewmodel whatever), and i hit the shit. I've lost the context, so I can't simply get current dir, file locations from .io without passing activity/fragment to model class.</p>
  
  <p>Anyone could tell me what are the methods of retriving data (as dummy content is made, but there is static crap) ? Let it be sync or async, anyway, I want my model to play here and there, what I see is that I hit the wall of missing context because of decoupling. I think I started the wrong way but i can't find the right track.</p>
  
  <p>The main figure here is that I want to use internal storage and sync it with external DB later. The good example of what i'm going to achieve is to render the recycler view and give the app the way to swap it with another view, so i need one clean data model.</p>