Know Your Context

As your app grows, you will start having classes that are not Android components and do not have direct access to some Context. Instead, they will be talking with your Web services, or storing things in a local database, or performing any number of other tasks that are important for your app.

In an ideal world, few of those classes will need a Context. For those that do, you will need to decide what Context they will use:

• Do they take a Context as a function parameter for a particular operation, so the caller chooses the Context?
• Do they take a Context as a constructor parameter, so the choice of Context has to take into account how long this object is needed?
• Do they do something more elaborate, such as use dependency inversion?