Is there any reason not to use the Application class to share variables across Activities?
For instance a handle to the DB or a single HttpClient.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is there any reason not to use the Application class to share variables across Activities?
For instance a handle to the DB or a single HttpClient.
According to the official documentation “you can use it to maintain global application state”. IMO you wouldn’t want to hold onto to too many heavy objects, globally. Ofcourse, “too many” is too fuzzy:) There are other ways of sharing (persistent) data: Preferences, database, files. You might want to check whether any of these are a better fit for your problem.
The other thing that you need to understand about when using Application object is its Life cycle. Unfortunately, discussion of that can be very subjective but fortunately, such as discussion has already been done
Good luck!