Multitasking, Multitasking, Multitasking…

Update (19/07) – If you follow me on Twitter, you would’ve seen this when it was first posted, but for those coming to this post now, you may be interested in the ‘tombstone’ process. Essentially, this is what happens to your application when the user opens another application.

Well, I’ve seen many comments and repeat comments regarding multitasking on WP7. However, a lot of the responses are ignored so I thought the best thing to do is to write a quick post about multitasking on WP7 (based on information available so far).

Will Windows Phone 7 have multitasking? Yes and No. I hope that’s cleared the matter up :D.

Multitasking will be available for certain built in features, such as listening to music while checking emails. You’ll also be able to control the music via the hard buttons on the phone, for example, without having to go back into the music app. However, third party developers won’t have the same level of capabilities when it comes to multitasking. Their applications can be placed in the background (paused) and then returned to the foreground. Whilst in the background, the applications can’t receive input or process any data (officially – more on this in a bit). So, you can switch between first party applications and a third party (contrary to some people’s belief that you’re stuck in one app at a time), but that doesn’t mean that it’s true multitasking. When a first party application is launched, the third party application is ‘paused’. From this state, the third party application may well be placed in a ‘suspended’ state  if the device requires more resources. In the suspended state, the application may become terminated. Therefore, as a developer, if your program goes into suspended mode, you may want to save settings and other data in case your app is the next to be closed by the OS.

Read more of this post