One of the most popular arguments against the iPad is that the device doesn’t support multitasking. I’ve discussed this subject many times before, and after Apple introduced its version of multitasking at the latest iPhone OS 4.0 event, we all know that what we’re going to get is much more like a system-wide persistent state feature rather than actual multitasking. If by multitasking you meant to be able to have multitple windows on screen at the same time, you won’t have that. You won’t be able to see more than one app at a time, and I’m definitely fine with that. If I’m writing something in Pages I don’t need to keep an eye on Twitterrific, and when I browse websites with Safari I don’t edit spreadsheets in Numbers.
There are some cases though where you’d want to work with an app and have another one open, running on its side, to take a quick glimpse at it every few minutes. When I’m on my Mac, it happens that I read stuff in DEVONthink and take a very quick look at the newest tweets in Tweetie. Maybe this it’s no exactly multitasking (I keep thinking that we humans cannot multitask), so I’ll just say it’s fast app switching which benefits from the larger real screen estate of a Mac. But would you imagine this on the iPad? Having Pages and a small widget on screen at the same time? Wouldn’t it become a mess, even with this beautiful 10 inches display?
Maybe. Maybe we just don’t need widgets at all, and screw you if you want a damn Dashboard running on the iPad. Let’s take a different approach: basing on the iPad UI guidelines, the implementation of split views and popovers is highly recommended. You know, the same stuff Mail, Instapaper and all the other apps do. And when you have a split view in front of you, isn’t that a very raw kind of multitasking? You basically have two views running at the same time, so I guess it’s quite fair to call it in this way. No let’s apply this to a browser, and here comes Multitasking Browser for iPad.