14 DAY TRIAL // Apple has recently blocked Google's Google Voice application from making it into its App Store, while also removing third-party applications related to the service, something that wasn't received too well by iPhone developers, it seems. Following Apple's move, FCC started an investigation on the matter, and asked Apple to explain the circumstances under which it rejected the application, while also petitioning AT&T and Google for more information on the issue.
After the Google Voice application was rejected, Google stated the following: “Apple did not approve the Google Voice application we submitted six weeks ago to the Apple App Store. We will continue to work to bring our services to iPhone users, for example by taking advantage of advances in mobile browsers. We will supply the information that the Commission has requested.”
It has been suggested that AT&T has something to do with the rejection, and it seems that FCC is trying to find out whether this is true or not. AT&T already said it did not “manage or approve” applications in the Apple App Store, yet Apple refused to comment on the move. We should also mention the fact that developers already dropped their iPhones because of the Google Voice issue, and that the App Store and Apple's policies are now a concern for a lot of people.
Here is what the request from James D. Schlichting, acting chief Wireless Telecommunications Bureau Federal Communications Commission, to Apple states: Dear Ms. Novelli: Recent press reports indicate that Apple has declined to approve the Google Voice application for the iPhone and has removed related (and previously approved) third-party applications from the iPhone App Store. In light of pending FCC proceedings regarding wireless open access (RM-11361) and handset exclusivity (RM-11497), we are interested in a more complete understanding of this situation. To that end, please provide answers to the following questions by close of business on Friday, August 21, 2009.
A set of six inquiries follow, and you can see the entire content of the request here.