Boot Camp Shows Apple's iPhone Defense is Bunk
While you were out enjoying the weekend (hopefully), we were here digesting Apple and AT&T's response to the FCC's query regarding the "rejection" of the Google Voice app.
If you haven't heard, Apple clarifies, saying the app hasn't been rejected, but rather:
The application has not been approved because, as submitted for review, it appears to alter the iPhone’s distinctive user experience by replacing the iPhone’s core mobile telephone functionality and Apple user interface with its own user interface for telephone calls, text messaging and voicemail. Apple spent a lot of time and effort developing this distinct and innovative way to seamlessly deliver core functionality of the iPhone. For example, on an iPhone, the “Phone” icon that is always shown at the bottom of the Home Screen launches Apple’s mobile telephone application, providing access to Favorites, Recents, Contacts, a Keypad, and Visual Voicemail. The Google Voice application replaces Apple’s Visual Voicemail by routing calls through a separate Google Voice telephone number that stores any voicemail, preventing voicemail from being stored on the iPhone, i.e., disabling Apple’s Visual Voicemail. Similarly, SMS text messages are managed through the Google hub—replacing the iPhone’s text messaging feature.
Apple goes on to make more valid points, concerning the security of the transfer of the iPhone's contacts to/through Google. To be sure though, what you see above is their biggest concern with the App. The problem is, it just doesn't make any sense, especially when you consider one of Apple's other products.
Perhaps you're familiar with Boot Cam: Apple's utility allowing you to boot your mac into Windows if you install a copy on your Mac. The biggest concern with Google Voice is the manner in which it duplicates the functionality of the OS/apps Apple has placed on the phone, and yet Apple freely, and helpfully, includes the ability to completely duplicate the entire functionality of the OS on their computers.
Something just doesn't add up. Apple doesn't block Firefox from the Mac, because as much as they might want Safari to be the biggest browser, they know how foolish such a move would be. Why then would they reject an app for the iPhone that duplicates phone functions? Apple and AT&T both say AT&T has/had no say in this app rejection/further study. There's really no other rational reason for Apple to decline the app. If Apple truly believes they have created a superior dialing app/contact app, etc, then they shouldn't be bothered by an app that duplicates those functions. Let the consumer decide which is truly the better implementation.
And let's get away from this idea that the iPhone requires a special walled garden because it is a phone. The iPhone is not a phone, it's a lightweight netbook with 3G access. In the future this is how we will see every smartphone.
When you categorize it as a computer, this behavior can't be justified. Surely Apple wouldn't think that all the software for a computer should be approved by, and purchased through the maker of that computer exclusively. Then again, maybe they do...