Since I was a heavy Windows Mobile user back in the PDA era, proper multitasking on a mobile device was second nature to me. At least on my PDAs, multitasking in Windows Mobile didn’t seem to affect the battery all that much (and they had wifi and BlueTooth), so it was never a special or significant feature for me – it’s a pocket computer, of course it does multitasking.
Why was multitasking on mobile something normal back then (Windows Mobile, Symbian), while with the iPhone, it became something special? Something of a holy grail? Why did it suddenly become so hard to do multitasking without affecting the battery too much? Why, almost five years down the line, does the iPhone still not have anything other than My First Multitaskingâ„¢ (which, for all intents and purposes, is barely one notch above a list of recently used applications)?
There are several reasons. First and foremost, whereas operating systems like Symbian and Windows CE were designed from the ground up to be small and efficient on constrained hardware (which explains why WP7.5 kicks Android’s and iOS’ butt in the performance department), operating systems like iOS and Android are basically comparatively heavy desktop and server-class operating systems shoehorned into mobile devices. This obviously comes at a price.
In addition, processors have progressed much faster than battery technology, and while my PDAs already had wifi (and I even had a Windows Mobile smartphone, the HTC Artemis), modern day wifi is more powerful and probably sucks more power. I don’t believe the story about how we use our smartphones more often. In fact, I used my PDAs more often than I do my phones today, because now I also have a slim ultrabook and an iPad to take on most of the PDA’s duties.
With my history as a PDA user, I don’t consider iOS to have proper multitasking – and by proper multitasking I mean that the user has the ability to run multiple programs simultaneously. This is important, because iOS itself, of course, fully supports multitasking and all that comes with it – it just doesn’t expose it to the user. I don’t consider the capability for applications to run a few select pre-defined, Apple-approved tasks in the background to be multitasking.
In iOS, application programmers can only perform the following seven tasks in the background:
- Background audio – application continues to run in the background as long as it is playing audio or video content
- Voice over IP – application is suspended when a phone call is not in progress
- Background location – application is notified of location changes
- Push notifications
- Local notifications – application schedules local notifications to be delivered at a predetermined time
- Task completion – application asks the system for extra time to complete a given task
- Fast app switching – application does not execute any code and may be removed from memory at any time
Many would argue that this covers most use cases, and while that may be true, none of them address the fundamental issue with iOS and multitasking: it feels bolted-on. An afterthought. Something added only to shut up all the complainers. Here, you can continue to play audio while you run another application. Now shut up, that’s multitasking..
However, on iOS, applications still don’t really know whatever’s happening to other applications. Switching between multiple applications really means switching between applications; when you switch to another application, the previous one is killed. It can continue to do any of the above seven tasks, but that’s it. On iOS, whenever I need to switch to a different application, I feel hesitant, because I never know what’s going to happen to the previous application. Will it remember the text I just typed in? Will it remember my location inside the application?
It’s all made worse by the fact that switching between applications on iOS is a very cumbersome process. Pressing the home button twice is not a comfortable operation, because it’s very error-prone for me – I regularly end up long-pressing the button, or the second press isn’t firm enough and I end up at the home screen. It feels like Apple never intended for this functionality to be part of iOS, but after all the complaints, was forced to add it anyway.
On Android, multitasking has clearly been a design consideration from day one (mostly, but we’ll get to that in a minute), and the back button plays a major role here. The major advantage comes from the fact that applications can do a lot more while they’re not front and centre than the seven tasks applications on iOS can perform. The key to why I prefer Android’s multitasking to the seven background tasks in iOS is Android’s concept of Application Components (see Dianne Hackborn’s article on the subject for a good primer, or the more in-depth article at the Android Developers page).
Application Components “are the essential building blocks of an Android application”. There are four different types of application components, the most important of which is the activity. Each activity is a single screen with a user interface. Each application (generally) consists of multiple activities; Gmail, for instance, has an activity which displays the list of emails, an activity for composing email, and so on. Twicca, my favourite Android Twitter client, has activities for the timeline, a user profile page, compose tweet, and so on. Heck, even your homescreen is just an activity.
Second, there’s the service, which, as the name implies, is a component which runs in the background to perform tasks that take a while, and do not have a user interface. Examples are audio playing in the background, or fetching data over the network. These continue to run even if the user switches to another application.
Third, we have the content provider, which manages a shared set of application data, which can be stored in the file system, an SQLite database, or any other persistent storage location. Other applications can access or modify this data through this content provider (assuming permission has been given). Lastly, there’s the broadcast receiver, which takes care of receiving messages from other applications (e.g., telling applications a certain download has completed).
The unique aspect of Android multitasking is that each application can start another application’s components. You can see this at work when browsing the web and encountering a link to a tweet, or a Twitter user’s profile page. While on iOS it will simply open the Twitter.com webpage, on Android, you can tell the phone to open your Twitter application instead – however, instead of launching the application as a whole and switching to it, only the relevant activity is launched.
So, in the case of tapping on a web page link to a tweet, Twicca’s activity for showing a tweet is launched and shown to the user – without actually launching the entire Twitter client. The same happens when tapping a link to a profile page; Twicca’s activity for user profile pages is launched, again without launching the entire application. In both cases, a single tap of the back button brings you back to the browser. In addition, if you open the Task Manager, you’ll see that Twicca didn’t actually launch at all.
It’s precisely this ability that makes Android’s true multitasking feel so smooth and natural. Instead of hopping from silo to silo (iOS) without really knowing what the application you’re leaving behind is going to do, which can be jarring, you’re just quickly opening a single activity, and hop back trough a single tap on the back button.
It’s difficult to explain if you haven’t used Android for any extended period of time, but this is really one of the things that pleasantly surprised me. I just figured applications ran in the background, and that the concept of using multitasking on Android was effectively the same as on iOS. In reality, though, it’s a lot more well-thought out and integrated into the operating system and its user interface than is the case on iOS.
It’s not all roses and unicorns, however. While opening activities from another application and hopping back is easy and fluent, switching between applications as a whole is just as annoying on Android as it is on iOS. You long-press the home button, and a dialog pops up containing the icons of the six most recently used applications. It’s a little bit worse than iOS, even, since you’re limited to those six applications, whereas on iOS you can scroll back pretty far.
On the whole, though, multitasking on Android is far superior to the seven pre-approved background operations in iOS. I honestly hadn’t expected it would make that much of a difference, but after a few months on Android, I find my iPad cumbersome and jarring when it comes to using multiple applications.
History is written by the victors.
BTW: Preaching to the choir somewhat?
Geeks btw come in different sizes, my friend describes himself as a design geek. I describe myself as a bicycle geek before a computer geek (you wouldn’t know the stuff I do about bottom brackets … swedish bicycle you say??)
Some people label themselves geeks because they are into gadgets. I would say some UK football supporters are geeks because they know soo much about it, it is on obsession.
I love the idea that there is some type of Geekism hierarchy and by knowing the history (that nobody except us care about) of how Smartphones evolved makes you the lord of nerds or something.
I hope you know about the true scotsman fallacy?
Early smartphone history will be nothing except a curiosity.
Edited 2011-12-19 20:33 UTC