[citation][nom]cadder[/nom]I'm not sure I understand fully but here is my understanding:iphone: If you have an app running and you start another app, the first one terminates. iphone apps have to be written so that sudden termination doesn't lose data, etc.Windows Mobile 6.1: (I have this on my current phone, I also have several old PocketPC's that use previous versions of this OS.) My understanding of the WM OS is that when you launch a new app, the old app stays in memory it just isn't running anymore, and if you switch back to it then it is still there and picks back up where it left off. Does anybody know if this is true?I don't know very many reasons why you would need true multitasking, i.e. the background tasks remain running, but if they would stay in memory ready to resume where you left off that might be good enough.[/citation]
for the most part this is true, in windows mobile, when a app is in the background, it pretty much goes in a sleep mode unless it is actively doing something that cant be paused.
for example if you start up a simple game and it is using like 20% CPU usage just sitting in the main menu, if you minimize it, it uses 0% CPU usage, but it's memory usage does not change.
the problem is suppose you only have 128MB ram and the game is using 100MB of RAM, but you now decide to launch fennec which is a resource hogging browser (that wants like 60+ MB all to it's self, since it is the active app, the game running in the background will have it's task ended automatically
the only time when a background app will hurt battery life is if it is something that will have a constant CPU usage while in the background, for example one of those crappy apps that does like a running water effect on the task bar
or a bit torrent app for windows mobile (which will use CPU cycles while it runs in the background)
Most windows mobile apps go into a sleep state when put in the background
Microsoft probably wants multitasking but is probably still thinking about how to do it in a way that wont cause apps to crash when low on memory. They probably also don't want to rewrite the kernel to allow for virtual memory
either that or just like with each new version of windows mobile, the OS uses more memory with each new version, and windows mobile 7 probably uses so much that it can only reliably run 1 app at a time. Mobile devices are low on ram and increasing the memory will also increase the cost, which will hurt profits when trying to be competitive as the average smart-phone user doesn't even know the specs of their smart-phone. At my college when I help some students out with their windows mobile based phones, many of them didn't even know that the smart-phone used RAM