Advertisements In the app I'm writing, I have a list that contains BScreens ready to be pushed. These BScreens in turn contain lists that contain BScreens. Repeat this for a couple levels. It didn't occur to me when I first wrote this, but I'm populating all of these lists in the constructor for each screen. So when I create the first screen, it's list is created and is populated with BScreens that contain lists, that contain BScreens that contain lists... In effect, when I push my first main menu screen, I'm creating all of my app's screens all at once. Using my test data it's not so bad, but with live data this could amount to thousands of BScreens in memory taking up resources. So my question is, does a BScreen that has not been pushed take up many resources? Would I be better off populating each BScreen's list in the handleEnter() method?