Tinman
iPF Noob
This is mostly true.Actually with the way iOS mutlitasking works you couldn't fill the ram if you opened every app on your device. It saves a very very small state file to the SSD (remember no moving parts on the memory so it loads instantly) so at any given time the only thing using actual ram is the OS and the current app...and if they current app is overflowing...well then it was written poorly and shouldn't have made it to the app store to begin with.
But apps can be written to run in the background. Indeed my iPhone 4 apps do exactly that, the ones updated for it of course. I have a radio streaming app for my i4 that I have been running on my iPad 4.2 beta 2 and it works very well. Interestingly, it continued to run when I played a youtube video embedded in a web page on safari. I could hear the video as well as the radio app.... don't think the iPhone will even do that (I think it would stop the radio app to play youtube).
Not just streaming apps can run in background either: dropbox for example, will download on my iPhone 4 after I leave the app. But it is not using the same RAM as when it is in the foreground: it uses just enough for the downloading/uploading task. Most iPhone apps that run in background seem to do likewise on my iPad running 4.2--as long as it is dedicated iPhone app. Apps that work on both iPad and iPhone don't seem coded for background operation on iPad yet.... but I am sure they will as 4.2 gets closer to release, or is released.
ReelDirector is even better on iOS4 on my i4: it will literally compile a movie in the background. And it doesn't seem to slow the whole system down either. When done it pops up a message letting me know it is complete. Very slick actually. Since ReelDirector works on both iPad and iPhone it won't run in background on iPad. Hope it does soon.
But you are correct of course in that most apps only need to save their state. And that doesn't tax the system at all.
Michael