Using Application context everywhere?


In an Android app, is there anything wrong with the following approach:

public class MyApp extends {

    private static MyApp instance;

    public MyApp() {
        instance = this;

    public static Context getContext() {
        return instance;


and pass it everywhere (e.g. SQLiteOpenHelper) where context is required (and not leaking of course)?

3/4/2010 5:39:38 PM

Accepted Answer

There are a couple of potential problems with this approach, though in a lot of circumstances (such as your example) it will work well.

In particular you should be careful when dealing with anything that deals with the GUI that requires a Context. For example, if you pass the application Context into the LayoutInflater you will get an Exception. Generally speaking, your approach is excellent: it's good practice to use an Activity's Context within that Activity, and the Application Context when passing a context beyond the scope of an Activity to avoid memory leaks.

Also, as an alternative to your pattern you can use the shortcut of calling getApplicationContext() on a Context object (such as an Activity) to get the Application Context.

9/19/2016 3:28:43 AM

In my experience this approach shouldn't be necessary. If you need the context for anything you can usually get it via a call to View.getContext() and using the Context obtained there you can call Context.getApplicationContext() to get the Application context. If you are trying to get the Application context this from an Activity you can always call Activity.getApplication() which should be able to be passed as the Context needed for a call to SQLiteOpenHelper().

Overall there doesn't seem to be a problem with your approach for this situation, but when dealing with Context just make sure you are not leaking memory anywhere as described on the official Google Android Developers blog.

Licensed under: CC-BY-SA with attribution
Not affiliated with: Stack Overflow