This is how you can speed up the loadingspeed of your application, as Activity's [font=Courier New]findViewByID[/font], like you probably used it up to now, is not that fast as you think. As you know the Android Layout-Structure is hierarchical (just like HTML and XML) and therefore the easiest way to represent it is a tree. The effect is bigger, as your layout gets more complex

Simpliefied Example Layout for this tutorial:


So if you do the following the Android-Runtime has to traverse the whole layout-tree every time you call findViewById (of your Activity). The better way is to call myView.findViewById when you habe nested a nested layout.

So, getting the both TextViews of the both TextViews from the example before worked like this:

Where the following is the faster way:



Regards,
plusminus

Doing it this way gives you another findViewById and instantiates a field for layot_outer. Does this impact optimization at all?

I only timed my app once using each method, but there's definitely some merit to this. My activity has three tabs and lots of views, so I expected some improvement.

Calling only Activity.findViewById: activity launches in ~4000ms according to adb logcat
Calling findViewById methods of parent views: activity launches in ~2400ms

Woohoo!

could you look at this problem?
viewtopic.php?p=34051
thanks