Why The iPhone Doesn’t Multitask

Filed under: apple, computers, mobile phones, software - 13 Jul 2009 2:11

I’ve had my iPhone 3GS for a few days now. It is turning out to be everything I expected. Perhaps because I did my homework before buying. I went into it with my eyes wideopen.

One thing I knew going into buying this handset was that the iPhone’s ability to multitask was mostly non-existent. The iPod function would play music in the background, Microsoft Exchange syncing would occur in the background. Built-in apps (and some third party apps) would appear to resume where they left off.

There are times where the ability to multitask would be useful. Streaming music over 3G with one app and using Trapster to look for known speed traps is one (FYI, the new release that’s compatible with 3.0 is HOT). Using something like a chat client and “some other app” is another. I’m sure you can name about a gajillion others.

We often treat our smart phones like computers. They are, in a sense, but they aren’t nearly as full powered as your desktop or laptop computer is. Consider that my personal computer is a first generation MacBook with 2 gigs of RAM and an external screen attached. Surely I can run–and see–a number of apps at once. It also has the benefit of a hard drive that allows me to use virtual memory to run more apps.

Meanwhile, the iPhone 3GS supposedly has 256mb of RAM. One of my first work laptops I had at Nokia had that much RAM. But unlike that laptop, the iPhone 3GS doesn’t have a hard drive for using virtual memory. Sure, you could use the flash memory for this purpose, but do you want to wear out the flash in your phone that much faster?

The Nokia E71 has only half the RAM of the iPhone: 128mb! Yes, it multitasks. I can tell you that phone starts bogging down when more than a couple of applications are running on it at the same time. The phone crashes or freezes and needs to be power cycled. Regularly.

While there are plenty of perfectly valid reasons to multitask, our mobile platforms today don’t have enough RAM–or CPU–for the task. Apple, having a singular focus on an excellent user experience, decided not to allow third party apps to run in the background. By focusing most of the memory and CPU on only one primary task–and a controlled set of others–Apple ensures your iPhone experience will be smooth. That isn’t to say your phone won’t crash, but it happens much less frequently.

And you know what? I think it’s a lack of multitasking is an acceptable tradeoff. My phone is more reliable. It doesn’t randomly freeze. It does what I’m asking it to do when I ask it to do it. It’s the way most people expect their phone to behave. Apple will support multitasking when our mobile platforms have a bit more memory, CPU horsepower, and, of course, better battery life.

Reblog this post [with Zemanta]


Bookmark with: del.icio.us Digg it Furl iFeedReaders ma.gnolia Maple.nu RawSugar reddit Simpy StumbleUpon
Tags: , , Fnord

7 Comments

  1. Comment by Jeremey

    Agreed, and I don’t think people have fully grasped the push notification model or the power available there.

  2. Comment by David Beckemeyer

    I’d be okay if they never open up multiasking as a free-for-all. I’m okay with those apps that want to mutitask to require an extra fee and extra testing and certification for exactly the reasons you state. Franky, people have forgotten how to program for relibability, for pacemaker type reliability. We don’ thave to. The OS recovers all our leaked memory for us when we restart the app, and computes have so much memory etc that poor practices can operate in real life without much trouble. As you note, not so on a smaller machine, where memory, CPU, and battery power consumption matter. I’ve written apps for Nokia that run in the background reliably for months on end, don’t consume all the memory, or burn up the battery, etc. But you have to REALLY work at it and have all those things at the forefront of the design and implementation – and that’s not the way most people write apps. Most people don’t even know enough about the guts of the machine to know how to write that kind of code.

  3. Comment by PhoneBoy

    You’re right, David. Nobody does the work to develop apps–mobile or otherwise–that are CPU, memory, and power efficient. Heck, even the OS vendors can’t get this right (yes, I’m looking at you, Microsoft and Nokia).

  4. Comment by Andy Abramson

    Trapster and push notification would be very, very cool.

  5. Comment by PhoneBoy

    It does today, it just only gives you new traps reported within a 30 mile radius (give or take). If it could do push based on your GPS location, that would be hot :)

  6. Comment by gerrymoth

    Today I’ve been using my Nokia 5800XM to listen to podcasts, tweet on Gravity, check email using Profimail and read greader using opera mini, while caling and texting now and then, ALL at the same time with no Crashes, Shutdowns or slowdown. Yes Nokia’s can multitask, with the right phone and the right apps.

  7. Comment by PhoneBoy

    The 5800XM has other issues, too: a poor touch-screen keyboard and abysmal battery life. There’s a reason I have *four* batteries for this phone. :)

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.

Switch to our mobile site