Just Another iPhone Blog

1,843 views

Provocative title no?

Caution: Brandon Mini-Rant Coming.

First off, let’s start this one with the obvious… MobileFailMe. I’m not going to beat this one to death, because well frankly, I don’t use it. But, given the amount of issues they’ve had it hardly seemed timely to light off a good rant and not mention the fact that this was such a HUGE FAIL. I mean come on. Jobs had to come out and basically admit they made huge mistakes and that the service is not up to snuff. I personally have the money sitting right here and I want to get on the MobileMe bandwagon… but I won’t won’t bother buying into it (and I own a Mac) until it comes with a whole lot less …

Next up … iPhone 2.0/2.0.1 - the most recent definition of head up the you know what. Apple made a vital mistake - they told us long in advance what date 2.0 was coming out, and come hell or high water the product was going to launch. There’s no way Steve was going to

let the egg get all over him for missing that launch date. With the iPhone 3G announcement hanging in the balance July 11th was THE DAY. Unfortunately, and I’m sure many developers can attest to this, setting deadlines for software to ship and announcing them to the public doesn’t always net you the best product at launch. That’s why so many developers follow the rule of set a date in house, but tell the general public that it will be ready when its ready. Unfortunately some folks just never learn but hopefully Steve has this time.

And now, even with almost a month to get the kinks worked out, the best Apple has managed to do is swap one set of bugs for a second set of bugs.

Yes, 2.0.1 has been out for a little over 24 hours and I’m already starting to see them. First example came this afternoon when I was going to call my wife. Notice I said going to … because after 3 attempts to dial the number I gave up. The dialpad would take 10-15 seconds between presses to actually acknowledge that I was trying to press the number. By that time I had hit the same number a ton of times in frustration. so the number looked like - 720000002144444444 - and I rebooted.

Like many folks I also shut off 3G when I’m not using it. After a few hours at work I decide to take a break and go outside to catch some sunshine and catch up on Twitter. But, seems that switching on 3G when its been off for a few hours really pisses it off. Because I had to reboot (again) to have the iPhone actually stop saying “no service”.

And our final head up the dark tunnel moment…. iTunes!

Tell me again Apple why I need multiple copies of the same app? I mean is it really necessary that I have 4 copies of the eBay application? Is that going to help guarantee a win or something? Somehow I doubt it.
This one has been covered a few times on Twitter and around the web and while its an easy fix, its not something I should even have to concern myself with. This is something that should be 100% transparent to the user AND it definitely is something I shouldn’t have to worry about checking just to make sure my apps are up to date.

And speaking of up to date iPhone Applications … WTF IS THIS?!

Seriously WTF is that? I updated AOL and Wordpress last night and a couple the night before. I’m not sure what the 7.7.1 update for iTunes did, but I’m pretty sure (judging by the picture) it wasn’t anything useful. So please, can someone at Apple tell me what the heck is going on in Cupertino?

If you enjoyed this post, make sure you subscribe to our RSS feed!