Android best practises: Loading stuff in background and storing results acceptable from multiple activities?
I am currently developing a application which is capable of locating nearby bus and train stops and display departure boards for a user. I have an activity, let us call it Activity1 that displays the 20 nearest stops. When one of these are clicked Activity2 are opened and the departure-board is loaded and shown. 

In both cases I am using AsyncTasks for data retrieval and parsing in background. What I however would like to do is to load some of the departureboards in the background while showing the nearest stops. These would then be available as soon as the user decides to see one. 
So I would like some kind of mechanism (thread or service) that runs parallel with the ui thread and loads these data. The problem is that this mechanism should be accessibly from both activities. What is the best approach for achieving this? 

I thought about creating a static class SideLoader with a runnable object and maybe a public list of loaded departureboards that is updated contentiously when this runnable object are executed. But this do not seam like a good practice or what? 

I would really appreciated if someone could comment on this solution or point me in some other direction. 
Thanks in advance. 

Best regards, kenneth
Android best practises: Loading stuff in background and storing results acceptable from multiple activities?
===

I am currently developing a application which is capable of locating nearby bus and train stops and display departure boards for a user. I have an activity, let us call it Activity1 that displays the 20 nearest stops. When one of these are clicked Activity2 are opened and the departure-board is loaded and shown. 

In both cases I am using AsyncTasks for data retrieval and parsing in background. What I however would like to do is to load some of the departureboards in the background while showing the nearest stops. These would then be available as soon as the user decides to see one. 
So I would like some kind of mechanism (thread or service) that runs parallel with the ui thread and loads these data. The problem is that this mechanism should be accessibly from both activities. What is the best approach for achieving this? 

I thought about creating a static class SideLoader with a runnable object and maybe a public list of loaded departureboards that is updated contentiously when this runnable object are executed. But this do not seam like a good practice or what? 

I would really appreciated if someone could comment on this solution or point me in some other direction. 
Thanks in advance. 

Best regards, kenneth