Home/ Questions/Q 1114377
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T02:59:50+00:00

Just a random question. I’m learning a bit of Android right now, and in

  • 0

Just a random question. I’m learning a bit of Android right now, and in most examples, it seems a lot of common items (such as buttons, editboxes etc) get requested within each function using (cast) findViewById().

Is it considered good or bad practice to store the result of that in an Activity’s member values? Simple example:

public class MyActivity extends Activity {
    private EditText myText;
    public void onCreate(blah blah) {
       // blah
       this.myText = (EditText) findViewById(R.id.mytext);
    }
}

and use the myText field from there on. I think it’d be good for performance (depending on findViewById’s inner workings, I’m quite sure it’s already very fast), but I haven’t seen it be encouraged yet. Also, it wouldn’t be the first time I encountered a situation where ‘caching’ something like this leads to problems (had a case where database connections weren’t released properly because I remembered a ConnectionManager or something in that fashion).

Secondly, somewhat related, if you want to remember something across methods in your Activity (and later on too, when the Activity is restarted later), is it wiser to keep up both a class field and a value in SharedPreferences, or would calling SharedPreferences each time for setting / getting the value where it’s needing be a better solution? (better being ‘cleaner, without impacting performance significantly)

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    That is completely normal practice and is exactly what you SHOULD be doing. If you’re worried about memory leaks, or holding references or whatever, don’t be concerned about that when dealing with views.

    However, you SHOULD be careful about holding references to other contexts because that COULD cause a memory leak. That doesn’t mean you shouldn’t do it, just be careful about when you’re doing it.

    is it wiser to keep up both a class field and a value in SharedPreferences, or would calling SharedPreferences each time for setting / getting the value where it's needing be a better solution?

    You should do both. You should keep a member variable for when you only need to read the data, just be sure that when you WRITE to the member variable, you also change the shared preference.

    Also, it wouldn't be the first time I encountered a situation where 'caching' something like this leads to problems (had a case where database connections weren't released properly because I remembered a ConnectionManager or something in that fashion).

    This is what I was saying first. It all depends on what you’re storing. Views are fine to store, contexts can be dangerous, and database connections and registered listeners can cause really weird bugs. It all depends on the specific case.

    • 0