How to maintain global application state

-

 

     In Android application, it’s sometimes important to keep a global application state. by global application state I mean to be able to have an entry point to the application which gives us a starter place to do stuff before the application starts. this is important in many aspects, for example, the application can start from different entry points, such as the launcher, a notification, or a service, or even by responding to a certain broadcast.

    There are many approaches to achieve this goal, one of them which a prefer is the Application Class, once extending the application class, we are able to load resources, setting different contexts , or even starting a certain service before the first activity starts, this is done simply by overriding the onCreate() method.

Example:

public class MyApplication extends Application {
    boolean hasAgreed;
    @Override
    public void onCreate() {
        // TODO Auto-generated method stub
        super.onCreate();

        // get data from a db (you'll probably want to keep it in a static class         
        MyDatabase db = new MyDatabase();
        ArrayList<MyObject> objects  = (ArrayList<MyObject>) db.getMyObjects();
        
        
        // start listening to location changes
        LocationManager manager = (LocationManager) getSystemService(this.LOCATION_SERVICE);
        
        // loading sharedpreferences and acting accordingly
        SharedPreferences prefs = this.getSharedPreferences("my_shared_prefs", MODE_PRIVATE);
        
        if (prefs.getBooelan("approved_agreement", false))
        {
            dosomething();
        }                            
    }
    private void dosomething() {
        // TODO Auto-generated method stub
        
    }

}

So in the first part we are getting some data from our database to be able to store it in some static class for further use or processing.

In the second part we are staring to listen to location changes by getting a handle to the LocationManager

In the third part we are checking to see if the user has agreed to some agreement, this data is stored in the sharedPreferences, according to this value we can decide which Activity to fire or to do some other logic.

In addition, the Application class has ErrorListeners which can catch different errors from the context of the application and handle them form a single context.

In conclusion, the usage in the Application class is highly recommended and can make the development of android application to the next level.

 

Comments

Post a Comment

Popular posts from this blog

Spinner VS AutoCompleteTextView

-
Image
       We’ve all been in a situation where we needed to show a list of some sort, a list which should be triggered by a user interaction (click, tap, etc..) A list is simple enough, probably even a spinner if we don’t want to spend that much screen real-estate on showing a list which the user clicks once and probably doesn’t need to see it after that. A spinner can be a real bug once there are too much entries for the user to choose from, how much is too much? that’s a good question – probably it differs from user to user, and probably this will have some performance issues with areal large number of entries, you cannot scroll forever to find what you’re looking for. A simple solutions for the problems mentioned above is an AutoCompleteTextView. it’s a control which is basically a combination of a TextView, EditText, and a Spinner all wrapped up in a single easy to use and configurable control. let’s see how it’s done:   first, in the layout file, create an AutoCompleteTextView
Read more

How to update UI from a different thread

-
     Google has set it’s tone on some tough guidelines for developing android apps, basically there aren’t any strict rules but one very easy to misunderstand. there is a single Thread which is called the “main” thread, or “UI thread” on some places. this is the thread which is in charge on the views and interaction with the users gestures. based on the guidelines of any mobile platform at the moment, all the work that shouldn’t be done on the main thread should be done on background thread. this can be achieved in many ways, you can use AsyncTask, Or A Handler, Or a simple thread with an implementation of the   run() method within the declaration of the runnable. ok, so if I’m pulling some server data, or performing long calculations, pulling stuff from or to the Sqlite database I’ll probably use an AsyncTask. but let’s say for instance that I want to simply update the UI once every couple of seconds (update a TextView or an ImageView’s content etc..), here’s a simple example of i
Read more

Utilizing Http response cache

-
     A typical mobile application will probably consume some resources from a web server using http requests. This repeated task has some drawbacks: Bandwidth has a cost, polling the same data over and over again results in a waste of user’s quota. the responsiveness and user experience is compromised once the user keeps waiting for data. If the requested data hasn’t changed on the server, then there’s no reason for us to fetch it. Of course, local caching of data is a must, but we also need to be able to refresh the data if it has changed on the server. A simple solution which comes out of the box for API 4+ is http response caching. Http response caching is a mechanism which enables us as developers to save a footprint of the response utilizing the abilities of the Http protocol. Basically, is holds a simple cache of the response which can be defined and enabled in code, and it prevents from fetching unchanged data from the server which was already fetched and processed into t
Read more