Google’s mobile search tool for the iPhone violates the iPhone SDK
Google’s new Mobile Search tool with voice recognition is coming under fire this week as the application apparently violates the terms of the iPhone SDK. The issue here is the applications use of the proximity sensor. According to the iPhone SDK, the only permitted use of the proximity sensor it to turn the phone’s display off when it is close to the face and back on again when the phone is moved away. The Google mobile app however, uses the proximity sensor to prompt the application to start “listening” while the user begins speaking search queries, as well as delivering audible prompts to your assist with searching. John Gruber and Erica Sadun have accused Google of using private APIs not included in the iPhone SDK in order to deliver this functionality, thereby violating the iPhone’s SDK and giving its application an unfair advantage over other applications that adhere to Apple’s standards. Google chimed in on Wednesday and admitted that its application does indeed violate the terms of the iPhone SDK. Google did not admit to the more serious offense of using private APIs, but it did use undocumented APIs which are not intended for use during the development of applications. D’oh! It is unknown at this point whether Apple will enforce the rules of the iPhone SDK or look the other way. If it does enforce the rules, Google’s latest application could be pulled from the App store and it may be forced to rewrite, at the minimum, the offending portion of the application.
Am I missing something here?
Google’s app is NOT the first one that uses the proximity sensor to activate the microphone.
A few voice recorder apps for example do the same thing. Check out Note2Self for instance. Rather than having to tap a button to record, you just bring the phone to your ear. The proximity sensor activates the microphone and records your note. Great for when you are in the car and don’t want to mess with tapping buttons.
I’ve found a few other apps that also use the proximity sensor. So I don’t believe that Google was given any special APIs or access. If so, how do you explain these other apps using the same feature for months now? If anything, Google copied them.
So why is Google being singled out when other apps have been doing this for months?
Jesus H. Christ I hate Apple…with a passion.
wow shane ill give you a B+ for that essay
Not a hater of Aple but come on, their SDK restrictions are more of a restriction for the consumer than anything else. I just don’t understand why everything has to be micromanaged with this phone. Sure, call it security or whatever else makes you feel good but all this really does is keep new uses for the phone from ever seeing the light of day. Maybe Apple will see the light one day.
Still better than the Bold, Storm or anything that runs Windows
The Google App does NOT use the proximity sensor. It uses the accelerometer to determine when the phone is moving and starts recording then. Check Engadget’s comments on the story, someone actually did a test and discovered that the proximity sensor does not activate the recording when the phone moves close to your face.
StevenStupid you’re missing the point. If the App is not affecting the phone in any way then why complain and even think about pulling it? I’m pretty sure they tested it and knew this before they allowed it into the App Store but now that everyone is saying something about it they want to complain also. And the engadget post does not even say it’s the proximity sensor being used so I don’t know what their issue is.
Personally I dont think apple will do anything, it’s not them complaining its two devs. Don’t hate cuase google is the next microsoft? Take a lesson you will lose going up against that giant. To tell you the truth I am a bit boggled at google for putting that app on a competitors phone. But then again this is why apple may look the other way.