Existing users, log in.  New users, create a free account.  Lost password?

column.ted: iPhone 3G and MobileMe: New features add little value

Posted 28 July 2008 @ 8am in Opinion

Ted Landau

July 2008

The more time I spend with my new iPhone 3G and the new MobileMe software, the more I find that neither of these upgrades were worth the bother. Now, before you start sending me hate mail, let me be clear:

I still consider the iPhone to be one of the greatest technology inventions of the decade. And the new iPhone 3G is even better than the original. The iPhone 2.0 software, especially the App Store, is a significant leap forward from iPhone 1.1.4. As for MobileMe, on balance (assuming the service can ever get past its initial hassles and actually work as intended), I believe it is marginally superior to the .Mac service it replaces.

So what’s the problem? The problem is this: The new hardware features in the iPhone 3G and the new options in MobileMe are largely irrelevant to me (and I suspect to a lot of other people as well).

iPhone 3G

Let’s start with the iPhone 3G. It has only two major new features: 3G network support and GPS tracking capability. Yes, it also has improved sound (I can now hear my iPhone ringing even in a noisy environment) and a standard-size headphone outlet. But these are small-change improvements. It’s 3G and GPS that represent the major differences from the original iPhone. So let’s look at these features.

If you had asked me before I bought an iPhone 3G, I would have told you that 3G support is a very big deal. Indeed, painfully slow Web browsing, when using an EDGE connection, was my single biggest complaint about the original iPhone. However, it turns out that the 3G capability makes far less difference for me than I had anticipated.

For one thing, the 3G network is not available in nearly as many places as the EDGE network. I often can’t get on the 3G network. Even if I do make a 3G connection, it is often such a weak one (just one bar with occasional dropping off altogether) that the overall speed seems not much different than with an EDGE connection.

Making matters worse, keeping 3G enabled on my iPhone is a significant battery drain. Plus (although I have not yet had problems here), iPhone Atlas reports that 3G can interfere with other iPhone functions, such as using GPS in Maps or making calls through a Bluetooth car audio system.

The net result is that I have decided to disable 3G on my iPhone (via the option in Settings > General > Network). I turn it back on pretty much only if I intend to use Safari and find myself in an area that has a reasonably strong 3G connection but no Wi-Fi availability. This combination doesn’t happen very often.

As for GPS, this too appeared at first to be a great addition to the iPhone. I was especially looking forward to using an iPhone as a turn-by-turn navigation aid — eliminating the need for me to purchase and carry around a separate GPS device. However, as you have probably heard by now, this turn-by-turn feature is not yet available for the iPhone. Without this, GPS in an iPhone offers very little. Remember, even without GPS, your iPhone can still find your current location in Maps and can still use Location Services in other applications (such as for geotagging photos). The non-GPS location ability is not as accurate as GPS and doesn’t offer "live tracking" but (at least for my use) it is usually good enough. Finally, there are locations (such as when surrounded by tall buildings) where GPS may not be available even though other networking options are. The end result, once again, is that I rarely take advantage of having GPS on my iPhone.

Eventually, I expect these features to offer more value than they do today (turn-by-turn GPS may even be in the next iPhone update, as reported by iPhone Atlas). But for right now, given my use of the iPhone, the advantages of upgrading from an original iPhone to an iPhone 3G have turned out to be close to zero.

MobileMe

Then there’s MobileMe. I am sure you have heard about the troubled start of this new service (read this article if you haven’t heard). But forget all of that. My disappointment with MobileMe would remain even if everything about the service worked exactly as promised.

Yes, there are some valid uses for MobileMe (just as there were for its .Mac predecessor). Assuming you are willing to spend $99 a year, rather than seek out cheaper or even free alternatives, you can use it to sync data across multiple Macs, backup your Mac’s data to an online source or post photos to a Web gallery. However, I am focusing here on what’s new in MobileMe, what you can now do that you couldn’t do with .Mac. In this regard, there appear to be only two significant additions: The Web apps (for managing your email, contacts and calendars from a browser) and the ability to push these data to your iPhone. I rarely need to access my data from a browser. Thus, for me, the single biggest new draw of MobileMe is the push function: the ability to have changes made on my Mac (or email that I receive) instantly and wirelessly transfer to my iPhone.

The first splash of reality here is that (as Apple has acknowledged) "instant" can really mean "15 minutes or more" — when going from your Mac to the MobileMe cloud and from there to your iPhone. But let’s ignore this too.

The critical questions for me were: How important is it for my iPhone to receive updated data (almost) instantly? And is it worth the downsides? The answers turned out to be: Not very and no.

I don’t often update my Address Book. And I rarely make calendar appointments on such short notice that I need to worry about getting them from my Mac to my iPhone within 15 minutes. Or vice versa. In any case, when I make such changes, I am typically at my desk using my Mac. If needed, I can sync my iPhone in iTunes after making the changes. As for email, I can set my iPhone to fetch new messages every 15 minutes from any email account, even without MobileMe. I have no need to find out about new messages more often than that.

Apple states: "Push is recommended because it helps reduce unnecessary network traffic, and updates data without you have to open an application." True enough. However, except for email, you don’t get alerted to when new data arrives on your iPhone. For example, if your spouse enters information to your calendar in iCal, while you are away from home, you won’t know about it on your iPhone until you open up the Calendar program and check. So you still wind up having to open the application.

Even so, I might welcome using these push features — if it weren’t for their downside. The biggest downside (as with the 3G network) is that the continual checking for new data uses up the iPhone’s battery at a faster rate. Beyond that, putting MobileMe between your iPhone and your Mac adds another layer of complexity and thereby another opportunity for things to go wrong. For instance, a recently posted Apple article states: "When syncing contacts with MobileMe on an iPhone, if you have assigned a specific ringtone to a contact, the ringtone for that contact may revert back to the default ringtone." Oops. That’s not what you want to happen.

I can imagine there are iPhone users who would benefit from a near instant wireless updating of their contact, calendar and bookmark data. However, most of these people are in the business world and are using Microsoft Exchange, and thus don’t need MobileMe.

Bottom line

The bottom line with MobileMe is the same as for the iPhone 3G: For most users, the newly added features offer little or no value to the service/device it replaces. This means that, if you currently own an original iPhone, I wouldn’t rush to replace it. And if you have happily lived without .Mac, I don’t see much reason to subscribe to MobileMe.

To send comments regarding this column directly to Ted, click here. To get Ted’s latest book, Take Control of Your iPhone, click the link.

[ Digg this  |  Bookmark on del.icio.us ]

Print This Post Print This Post

8 Comments

Posted by likeafox24
28 July 2008 @ 9am

“The non-GPS location ability is not as accurate as GPS and doesn’t offer ‘live tracking’”

This is not true! Even first-gen iPhones will live-track your current location and update the “cross-hairs” automatically as you move! Just make sure the current location button in the bottom left is highlighted in blue.

So, the iPhone 3G will still track you live and update your current location even when GPS isn’t available…and it’ll switch in and out of GPS if/when a signal is available.

Get yo’ facts straight, boi! (and enjoy the feature you didn’t know existed)

Posted by likeafox24
28 July 2008 @ 9am

Thanks, Ted, for the article. Other than the factual error I corrected in my previous comment, I really enjoyed and largely agree with your opinions.

I would point out, however, that I think Apple deserves some credit for not leaving original iPhone users out in the cold. The way I describe the new iPhone 3G to people is that it takes an incredible product in the iPhone, and makes it a little more than just marginally better.

BUT, the BIGGEST deal about July 11 is the iPhone 2.0 software with third-party apps.

And that is indeed the genius of the device to begin with. If you buy (or bought) an iPhone (first OR second gen), then you get to ride the wave of technology and new software on the cutting edge for a good while to come! That’s what’s so great about it.

But I totally agree with you. If your circumstances are like mine or like Ted’s, then sticking with a first-gen iPhone allows you to harness (at a lower monthly cost) the lion’s share of what July 11th introduced into the mobile world.

Posted by bongoherbert
28 July 2008 @ 10am

I find the whole ‘reduced network traffic’ thing with push to be interesting.

I have a 2G phone, use MobileMe with the contacts et alia set to ‘Push’. When I go to bed I might have 3/4 battery life, but wake up and I’m at the 10% warning if I’m lucky.

Turned off ‘Push’ and no such issue any more. Sort of interesting…

I live where there is terrible cellular service, so there may be some straining of the radio to connect to Edge, but I have a strong WiFi throughout the house, so I can’t imagine that it would necessarily need to try to connect with the cellular radio. ‘Want’ is one thing…

Posted by jfmsam
28 July 2008 @ 12pm

As a hobby developer, Apple iPhone Beta tester, and Apple fan, I feel compelled to add this extended comment to clear up what I believe to be misconceptions.

MobileMe:
I personally don’t care for the upgraded wep apps. If I am on a computer, I am usually in my own in my office or home office or with my laptop.
I like MobileMe for the Sync (a must with three computers and an iPhone), Push, iDisk, Back to My MAC and Gallery features.
Too bad they got a bad rap with their rocky start.
If you have or plan to get an iPhone it’s a neet complement to have, especially if there is more than one iPhone or MAC in the household.

iPhone 3G:
I believe the new iPhone 3G was not intended as an upgrade for the previous generation iPhone owners. It was meant to lure new customers who may have felt that the first generation device was not up to par (Lack of “official” applications, lack of Push/security, aGPS and 3G for the most part).
Comparing it as an upgrade to the previous generation is not fair. It is more a matter if the new device justifies for new users to be willing to sidegrade from their current devices.

I also think Apple did a great service to previous iPhone owners by giving them OS 2.0, thus not putting an unnecessary strain in their budget if they wanted to access many of these new features and be forced to buy the 3G model. I agree that unless you really need 3G or aGPS, there is no need for an existing owner to upgrade to iPhone 3G.

3G battery drain:
It is not Apple’s fault; My Moto q9 global 3G drains much faster. Do some research and you’ll see that the iPhone tops competitive devices in similar GSM networks.

For either 2G or 3G, battery drain is mostly a factor of the power requirement to successfully sustain a wireless connection under interference conditions.
3G operates in a higher frequency thus requiring more power (I won’t get into detail about signal to noise ratio and carrier power requirements), consequently if the user already had coverage issues, these will worsen with 3G, unless AT&T has upgraded the area with more towers in the 3G spectrum.
In my case AT&T’s 3G has phenomenon coverage and speed, so it’s just a matter of time for most.

Push and battery usage:
The keep-alive that the device uses to notify the mail server is so small and occasional that I doubt it is the cause for the battery drain (hence my comment above). Actual data will only pass if there was something to push. Out of personal experience, checking my email every 15 min drained my battery faster; worse if you leave WiFi turned on.
Haven’t confirmed it yet, but the key to using Push properly is that in my settings I did make sure I left Push ON and fetch to Manual. That way I am not fetching every 15 min as well.

On a final note on the battery subject:
I’ve placed my 2G iPhone side by side with my 3G iPhone identically configured and left them alone from 6pm to 7am to compare battery drain. On average I get 2 or 3 pushed emails during that time to either my .MAC or Exchange account. In the morning I had minimal battery usage and the drain was similar in both cases, to the point that I had continued usage of my iPhone 3G during the day without the need to charge until late that night.

Posted by DistortedLoop
28 July 2008 @ 12pm

Funny that the comment from bongoherbert says Push kills the battery, and the next comment from jfmsam says that it doesn’t.

My understanding of how push works is the same as jfmsam’s - the client sits idling waiting for a notification (via a hidden SMS) that there is a new message, and then it wakes up to accept the new message. This would certainly seem to use up more battery than a frequent “fetch” model that has the radio turned on and asking if there is a new message every 15 minutes or 30 minutes or whatever you select.

It would be nice if some definitive source explained the exact mechanics behind this, or better yet, someone like CNET labs did some comprehensive testing to see if two iPhones with the exact same configuration, except push vs fetch, had dramatically different battery lives. jfmsam’s test shows that the firmware drains Edge and 3G phones at the same rate, but doesn’t help those of us extremely disappointed with the 3G’s battery life decide what settings are optimal for us in terms of convenience versus battery life.

Posted by DistortedLoop
28 July 2008 @ 12pm

“This would certainly seem to use up more battery than a frequent “fetch” model that has the radio turned on and asking if there is a new message every 15 minutes or 30 minutes or whatever you select.”

Ooops. That should have been: This would certainly seem to NOT use up more battery than a frequent “fetch” model that has the radio turned on and asking if there is a new message every 15 minutes or 30 minutes or whatever you select.

Posted by bongoherbert
28 July 2008 @ 4pm

As I said, just an observation and not a true experimental validation of ‘push’ battery use, also note I’m using an original iPhone and not the 3G. As I understand the functioning of the device/OS, it should work as jfmsam says. But this is not my experience as yet. I’m curious if there are other Original iPhone folks who see the push battery issue.
There very well could be something else afoot, some sort of evil app, or perhaps compulsive sleep-monkey-ball-playing.

Posted by jfmsam
28 July 2008 @ 9pm

*3G devices will drain battery faster regardless of the device:
http://www.pcworld.com/zoom?id=148348&page=1&zoomIdx=1

*If you have poor reception, regardless if you have 3G or 2G your battery will drain faster.
With iPhone 3G, Apple may address the 3G-2G handoff better in future OS releases. This should help to avoid pushing the power for 3G when 2G should handle it better.

A good head to head test of Push vs 15 min check would be interesting. But it all depends on the volume of email you have per day.

A quick, non-scientific, insight on how the outcome could vary:
-If in 30 min you get 10 emails, neither push nor fetch would have made a difference, because within those 30 min your total data transfer (& power usage) would have been pretty much the same.
-On the other hand if you get 10 emails per day (say from 8am to 8pm), with fetch you would have accessed the mail server 12h*4fetch/h= 48 times and out of those only ten times did you get your emails. With Push, during those same 12h, you would have only transfered data for those 10 emails plus the tiny keep-alives; hence Push would have saved you some battery life.
-Finally if you get more that 50 emails during those 12hrs, I don’t think either Push or Fetch will help you save your battery. Then again, in this case I would asume that with that load of mail, Push is a necessity because you are almost chatting with your correspondents.

Note: neither push or fetch will download the complete email. What you are actually getting are the headers and a few preview lines. The actual download comes when you go to read the email.

For better illustration I wish I would have kept a sample of the log of the early beta implementations of Push on the iPhone. There you could clearly see how small the data packet was.

In fact, I once did a non-scientific comparison, by putting the iPhone next to my land line phone and you could hear the speaker make noise on every transmission caused by the RF interference every time the iPhone “spoke” to the cell tower to notify it’s condition, versus when it sent the keep-alive data burst to the mail server. Upon every noise I confirmed its activity on the console and I could barely tell when the Push keep-alive happened. On the other hand, if set to fetch you could clearly tell the amount of RF just to see if there was anything new to fetch.

Hope these additional contributions help…

You must log in or register to post a comment.