Google admits to violating App Store rules
updated 04:15 pm EST, Wed November 26, 2008
Google vs. App Store rules
Google has admitted to using undocumented APIs in the creation of its latest iPhone search app, according to a spokesman. The company is specifically said to be relying on an API connected to the motion sensor, which tells the app to engage voice detection whenever an iPhone is raised to a person's mouth. Users can thus speak a search term, instead of typing it in.
The difficulty in this lies with the rules of the iPhone SDK, which state that developers can only use the APIs provided in order to create software for the App Store. It is this very reason, in fact, which is said to be preventing Adobe from bringing Flash to the iPhone. Google does have a far closer relationship with Apple, as Google Maps is integrated into each device sold; the firm has not, however, made claims either way of receiving special permission to break SDK guidelines.
Google has meanwhile denied a related allegation, one suggesting that Google Mobile links to private and/or dynamic frameworks. This kind of strategy is said to be frowned upon by developers. The company may nevertheless be forced to revise Mobile, should Apple decide that Google has violated its terms.










Who cares
11/26, 06:43pm reply
I just want the voice search to work with normal English instead of American English :-(
coldfusion1970
Fresh-Faced Recruit
Joined: Nov 2004
Say What?
11/27, 10:24am reply
"normal" English? You mean r***** english. Tally-ho, you snaggletooth mo fo!
Guest
Fresh-Faced Recruit
Joined: Nov 1999
-
11/27, 05:41pm reply
as for the google app, if it works more power to them. Apple already controls what goes on the iPhone, so if their quality control is functioning correctly, malicious apps will be stopped before turning up in the app store anyway.
Kees
Fresh-Faced Recruit
Joined: Sep 2001
so where does...
11/27, 10:03pm reply
...the undocumented API come in?
If Apple has an API built and simply has not reelased support or notation for it - but it still existsnonetheless how does it violate the ToS?
Unless the ToS specifically states that the use of any undocumented API is prohibited in a final release App but is available for testing purposes only.
UberFu
Fresh-Faced Recruit
Joined: Oct 2002
and...
11/27, 10:07pm reply
...if nothing happens to this Google App after they aparently admit to breaking something in relation to Apple's "corn-cob-up-the-a**" policy - then this simply adds to the fire that Apple needs to Publicly Doument the exact criteria they use to screen and admit or reject Apps from the Store.
INstead of the current method of some experiencing P.M.S. while throwing darts at a dartboard and blind-folded.
UberFu
Fresh-Faced Recruit
Joined: Oct 2002
API
11/28, 10:10am reply
as for the google app, if it works more power to them.
No, it just shows a distinct double-standard. People hate double-standards.
Apple already controls what goes on the iPhone, so if their quality control is functioning correctly, malicious apps will be stopped before turning up in the app store anyway.
That would include this app, right?
If Apple has an API built and simply has not reelased support or notation for it - but it still existsnonetheless how does it violate the ToS?
An undocumented API is basically an internal API or part of an internal framework. It is meant for the OS only, not public use.
Apple (or any OS vendor) does not want anyone using internal frameworks. The main reason is that the public API is NOT supposed to change (thus, when a new OS version is released, existing software works). However, internal frameworks/API for use by the OS only can be changed or modified without causing problems for developers and users. But if developers start using the internal API, then things break when changes are made.
Of course, the mac-faithful will always point to the developer, but a lot of users aren't part of the faithful. All they know is that they installed an OS update, and now their software doesn't work.
Unless the ToS specifically states that the use of any undocumented API is prohibited in a final release App but is available for testing purposes only.
Actually, the TOS does specifically state that. Thus the issue. In fact, it isn't technically available for testing purposes either. It isn't provided for any reason. People just find out that it is there and decide to use it.
BTW, if some regular developer did this, people would call their software a 'hack' and would denigrate it. Oh, but this is Google, so it is OK.
Guest
Fresh-Faced Recruit
Joined: Nov 1999