Google deals with this situation pretty well on Android. You have 16 MB of heap to work with, and you have to deal with their garbage collection. I agree with

Google deals with this situation pretty well on Android. You have 16 MB of heap to work with, and you have to deal with their garbage collection. I agree with the person writing the article. I'd rather have 16 MB of guaranteed RAM available, than maybe 40, or maybe 2. My iPhone app sometimes can't even initialize my tab view controller without crashing depending on the state of the users' iPhone. You can usually get away with using the keyed archiver to page in and out once your app is loaded, but it is typically getting loaded that is the challenge.