“Google acknowledged breaking the official rules of Apple’s iPhone software development kit when it created the latest version of the Google Mobile application for the iPhone, but denied a more serious charge,” Tom Krazit reports for CNET.
“A Google spokesman confirmed Tuesday that Google Mobile uses undocumented APIs (application programming interfaces) in order to use the iPhone’s proximity sensor to prompt a verbal search. iPhone developers were only supposed to use the APIs that Apple published in its SDK when they create their applications under the terms of that agreement,” Krazit reports. “Google has denied, however, a more serious charge that it was linking to private or dynamic frameworks in the Google Mobile application. That’s considered a big no-no in the development community.”
“Given Apple’s uneven process for approving applications onto the App Store, the question has continued to come up as to whether Apple’s ability to keep up with the flood of applications into the App Store has been stretched to the breaking point. It’s not clear whether Apple knew Google was using the undocumented APIs when it approved Google Mobile, or whether it simply missed that code,” Krazit reports. “Google might be forced to rewrite the code for Google Mobile or change the way the application uses the proximity sensor if Apple decides to enforce the terms of the SDK.”
More in the full article here.
That’s one of the coolest thing about the app!
Just fire up the app, bring it to your ear and start talking. Very slick. I hope Apple doesn’t make them change it.
It would be cooler if the results of the search could be read to me by the phone so I don’t have to look down while driving.
Bad Google!
You need to go to Cupertino and write “Thou Shalt Not Disobey Steve Jobs” a thousand times on the chalkboard.
Better yet, Apple needs to document the API for the proximity sensor so that Google is no longer violating the rules. This is a great feature, and they should not have had to break any rules to implement it.
Are these undocumented APIs anything like the undocumented workers? If so, shame on Google for taking employment away from American APIs.
They took ‘ur jobs!
And I read it as, Apple cleared some special undocumented APIs just for Google to enjoy. Good for Google to take the flak though.
MDN MW: public. Carry on.
I think Apple gave Google access to some of these un-advertised APIs. Apple will never slap Google’s wrist over something like this. These things happen all the time where some companies get special treatment based on their relationship.
@Nic,
That is precisely what I was thinking! The majority of end-users care about functionality more than programming code. If Google truly had to choose between either using the undocumented APIs or releasing the app, releasing the app was definitely the correct decision.
I disagree with all you lot who think Googles App is fantastic!
It would be if I could trust Google, but I don’t, not for a company that allows Chinese officials to lock up their citizens who dare surf un sanctioned sites whilst at the same time denying the US government the same access to fight drug smuggling and money laundering!
That is one app I will avoid like the plague!!!!!!
“And I read it as, Apple cleared some special undocumented APIs just for Google to enjoy.”
It’s good that the rules are clear and all iPhone developers are equal. Can’t someone just port Android to the iPhone and put an end to the random app store approval/disapproval process?
Man….I loved that episode. This shiznit was hilarious!!! “They took your jobs!”
HEELLLO! Google’s CEO sits on Apple’s board of directors. Don’t you think that they JUST MIGHT be privy to some inside information which would just happen to work to both companies’ advantage?
Come on guys, just put 2 and 2 together…
Nothing particularly strange about Apple choosing to partner with some developers to get a cool feature implemented if Apple want it.
I had expected more of this, where Apple and some partners might identify some cool features that Apple doesn’t have the resources to work on.
What I find worrying about this story is the idea that “linking to private or dynamic frameworks is considered” a “no-no” by the development community.
If it’s not allowed, then it should not be possible. Are databases the only programming environments that implement a basic application security model?
The whispering in your ear whilst the app searches is a little creepy i have to say!
” width=”19″ height=”19″ alt=”smile” style=”border:0;” />
Regardless of that, it’s a good app. It would also benefit from a bit of localization fine-tuning. I’m in the UK and don’t consider myself to have much of a discernible accent but still have a few problems.
Still, my imitation American voice is coming along nicely now
If you could look into your Mac applications, you’d find some of those also use undocumented APIs as well. It’s been going on for a very long time.
Sometimes, it’s the only way to add certain features to an app, as Google has just proven.
All this situation is doing is bringing a very old issue to the front of everyone’s minds, which is probably a good thing.
I guess if google is admitting it, but I assumed that google did not sign the same SDK agreement that regular schmoos did. Since they were in on it before the beginning, they must have a separate contract.
You can thank techno-dilettante bloggers like Harry McCracken for whining, arching and screaming at Apple for not releasing the recent update to Google App until – get ready – THE NEXT BUSINESS DAY. He made it seem like it was the end of the world. But ask Mr. McCracken if he feels bad that Google made a Bozo no-no in its programming (possibly opening up countless iPhone users to security risks) and I’m sure you’ll hear dead silence. Or you’ll hear him blame Apple for this.
My point is this: It’s up to all of us to hold pundits and self-annointed bloggers accountable. If that means ganging up on these twits and shaming them, great. They have the power of the pen and the press. We have to use people power to discredit the Enderles of this world, so that their big mouths and lack of common sense is laid bare.
Have a happy and safe Thanksgiving, everyone!
A paranoid person might think, as Google ‘pre-announced’ this app while it was still in the approval process and a well orchestrated chorus of bloggers and media outlets then loudly wondered what was taking Apple so long to approve it, Google chose to blackmail Apple into allowing use of an undocumented API (subject to arbitrary changes without notice). Google can tie Apple’s hands when it comes to improving the unpublished API for the proximity sensor, or simply blame Apple if the Google app ever stops working after a future update. Google is not playing straight with Apple or iPhone customers.
“You can thank techno-dilettante bloggers like Harry McCracken for whining, arching and screaming at Apple for not releasing the recent update to Google App until – get ready – THE NEXT BUSINESS DAY.”
Which means they forced Apple to cave on their no private API use policy and let this one out. Good on them. It sets a precedent for other developers using private “apple only” APIs.
A Google spokesman confirmed Tuesday that Google Mobile uses undocumented APIs (application programming interfaces)
If you could look into your Mac applications, you’d find some of those also use undocumented APIs as well. It’s been going on for a very long time.
Remember when MS was evil for having hidden API’s for themselves and their close allies?
You get the idea.
Google admits breaking Apple’s App Store rules with Google Mobile App
This of course means Google Mobile needs to be blacklisted and pulled from the App Store.
Fair is fair, Apple. Or are some developers more equal than others?
Isn’t it just possible that this API is under development and all developers will be able to access it in the next few months?
That seems the most likely answer.
Also read this about other bad Google behavior. Read the entire article, Google is watching you.
http://www.macworld.com/article/137094/2008/11/safari_safe_browsing.html