Yet more iPhone monkey business from Apple

A Techcrunch article (which references this prior article as well) slams Apple yet again for more iPhone App Store idiocy, this time centered around the Hottest Girls app.

It completely confuses me what Apple is thinking here: add parental controls to the 3.0 version of the iPhone OS, then when an application adds nudity to take advantage of this, pull the app from the App Store. Huh?

The addition of a nudity category and then pulling an app that has nudity is at best confusing. At worst, it looks like Apple is entrapping developers, or being selective on what apps get to stay in the store.

I’m not sure I can recommend anyone trust Apple at all for anything anymore.

A backdoor attack on net neutrality

Wired.com reports on Apple’s arbitrary iPhone application approval/rejection process, and how some believe it to be a de facto attack on net neutrality.

A group called Free Press calls out the inconsistent decisions Apple has when deciding which iPhone applications to approve or reject and why. In particular, an application called SlingPlayer was rejected by Apple in its original form. After Sling crippled it to only work on Wi-Fi and not the 3G or EDGE cellular connections, Apple was more than willing to approve it. Another Wired.com story says an anonymous source says Apple rejected the application in its original state at AT&T’s request, due to network congestion concerns.

This sounds reasonable, but there’s another half to this story. Apple approved the Major League Baseball application as-is, allowing it to stream live sports events over 3G and EDGE as well as Wi-Fi.

Another curious rejection is Ben Kahle’s “Me So Holy” app, the premise of which was to allow users to make Jesus-like portraits of themselves. Apple rejected it to “protect the sensitivity of the customers” in its “worldwide market.”

This is exactly why OpenMoko came about. The Neo FreeRunner (and/or its successor) is the smartphone I’m saving up for. Granted, they aren’t cheap (if they appear much less expensive than an iPhone and you’re reading this before 2009-07-15 or so, that’s a clearance deal for the previous hardware revision). But I would honestly rather take a price hit than voluntarily limit myself to what some giant corporation decides is suitable to have on my phone.

Apple rejects C64 emulator on iPhone

Few computer users from the 1980s will soon forget the rivalry between the myriad computer companies in business at the time. Apple and Commodore were at the forefront of that rivalry, as IBM’s PC didn’t really take off until later in the decade.

In fact, my earliest BBS experience from 1991 involved a fellow user–at the time he was actually a sysop–making a “Commode Commodore” joke to a friend (or maybe rival) of his who insisted upon using one of the things well past its prime. (Commodore was still in business making the Amiga line until their bankruptcy in 1994.)

So maybe it is only fitting, in a bizarre way, that Apple rejects a Commodore 64 emulator for the iPhone, as reported by Touch Arcade. It would almost be humorous except for the fact that the programmer spent several months on his project only to be censored by Apple. And I do use the term censored for a reason: this is censorship, and I fail to see a good reason for it. Several other emulator applications exist for the iPhone, and Apple still continues to leave them be.

Yet more evidence that Apple requiring the “seal of approval” on every iPhone application is unsustainable.

Apple rejects iPhone apps with no reason given

Ars Technica reports on Apple rejecting iPhone applications without offering an explanation. Of particular note:

Marco Arment, lead developer of Tumblr and creator of Instapaper, chronicled the situation on his blog. On the last day of WWDC ’09, Apple had a session dedicated to the process of publishing an iPhone app to its App Store. The session ended early, and lines of developers formed at the microphones to ask questions—ostensibly concerning App Store rejections and how best to resolve issues identified in the review process. However, at the end of the presentation, the presenter and other engineers quickly exited the room, leaving the assembled developers scratching their heads.

“It was a giant middle finger to iPhone developers,” wrote Arment. “Clearly, they had absolutely no interest in fielding even a single question from the topic that we have the most questions about.”

And later, as reported on tuaw.com, one unlucky developer got this in their e-mail:

“As you know, Apple reserves the right, in its sole discretion, to reject any application for any reason.”

So if you plan to develop for the iPhone, this is what you’re getting into. You’re at the mercy of Apple, and they may not even tell you why you can’t sell the application you just spent hours or days working on.

No other computing platform, anywhere, has one company deciding what can and can’t run on it. (And yes, I realize it may seem odd to call the iPhone a computing platform, but that is in effect what it is: a computer that can also make telephone calls.)

I believe the developers, at minimum, have the right to know why Apple rejects an application. However, I also believe a far wiser choice, one that might just get Apple’s attention, is for developers to stay away in droves until Apple takes a more hands-off approach with regards to the iPhone platform.

Personally, I believe the only valid reason for rejection of an iPhone application is if it has the potential to cause harm to the mobile networks that the iPhone connects to. I should note here, “harm” does not include the following:

  • letting the user make phone calls over a VoIP network like Skype or Gizmo;
  • content that Apple finds objectionable or that in Apple’s judgment does not belong on a mobile phone;
  • parodying Apple, AT&T, O2, or other carriers which Apple partners with;
  • any of the other reasons Apple has for rejecting applications for the iPhone.

It’ll probably be a cold day in hell before that actually becomes reality, however. I’m not going to wait.

Mobile phone exclusivity agreements under fire

Reports from both ITworld and Infoworld detail an inquiry from four US Senators to the FCC, regarding the exclusivity arrangements wireless phone manufacturers (such as Apple and Palm) have been making with wireless telephone carriers (such as AT&T and Sprint).

This follows an FCC petition by the Rural Cellular Association asking the former to investigate these exclusivity arrangements.

The timing couldn’t be worse for AT&T, as the telecom giant is dragging their feet to support MMS and tethering, among other things. Apple’s other carrier partners worldwide have been able to handle this without issue.

However, it should be noted that AT&T is not the only wireless telephone carrier in the crosshairs of the Senators and the FCC. T-Mobile and Sprint are known to have made exclusivity deals as well, which would undoubtedly be subject to the same scrutiny.

All of this is definitely a step in the right direction towards respecting the freedom of wireless phone users, or in other words, the rest of us. It is long overdue, but there is still a lot of work to do once exclusivity agreements are seen for what they are: anti-competitive collusion.

There is still a lot of cleaning up to do after this, however. Most notably, it would greatly benefit the wireless telephone users if there was one and only one standard in use: GSM. CDMA needs to go the way of the dodo, the sooner the better; the network design takes a significant amount of freedom out of the hands of the user, where it belongs. I consider myself rather technologically literate, and I did not know this until fairly recently (about a year or so ago).

GSM networks and phones use SIM (Subscriber Identity Module) cards for authentication and identification (or how the network tells which phone belongs to which user). If one wants to change phones, one simply powers down the old phone, removes the SIM card from the old phone (usually hidden behind the battery to make it impossible to remove while the phone is powered on), inserts the SIM card into the new phone, and powers the new phone on. The carrier (phone company) never has to get involved.

On a CDMA phone, it’s nowhere near that simple. One has to take the new phone into the store and have a staff member key in a bunch of magic numbers, and make changes on the wireless network so the new phone is recognized as legitimate. The wireless telephone carriers have the control; they can choose not to let you use the new phone on their network at all if they see it fit. It is, in fact, in the carrier’s best interest to get the customer to buy a brand new phone instead of re-activating an older model.

I have been told that Sprint will not activate non-Sprint phones for their service (i.e. phones not branded for use with Sprint). I would not be surprised if Verizon (and any other CDMA carriers?) adopt a similar policy.

Fortunately, we may actually see the demise of CDMA in our lifetime. Verizon is already in the process of changing over to GSM; that would leave Sprint as the last national US CDMA carrier in existence.