Google’s Android Kill Switch
October 16th, 2008 | by jasoneneal | Published in iphone | 6 Comments
Readers of FOI may recall the introduction’s focus on the iPhone as the book’s first example of a tethered appliance. The release of Android was viewed with some excitement as a challenge to Apple, in more ways than one.
Google, and later the Open Handset Alliance, have touted Android as an open source alternative to the iPhone’s tight control of applications. Android, for instance, allows users to download applications from developers without a central gate-keeper deciding what applications can and cannot be run. Even key components like the dialer or the home screen can be replaced. Sounds like a great victory for generativity, even in the face of the iPhone’s popularity, right?
Maybe not. A few outlets are reporting that Android Market’s terms and conditions include reference to a kill switch. Essentially, anything downloaded from the Android Market can be removed from a phone at Google’s sole discretion if it is found to violate the developer distribution agreement.
The articles linked above point to some of the interesting questions that arise from this: How will a list of “banned” applications be communicated between Google and the phone? Can applications not downloaded from Android Market be deleted at Google’s discretion as well? But to me, one of the most interesting questions (which the CW article does ask, briefly) is what the reaction to this kill switch will be from the user community, many of whom have been excited about Android because of its contrasts with the locked-down iPhone operating system.
Will Google face a backlash? We’ve discussed the iPhone’s kill switch here at the FOI blog before. A kill switch is merely one facet of what a fully tethered application can do. I’m still working out exactly how I feel about this seemingly weaker or more partial tethering of Android phones. Maybe this could be a decent compromise that allows Google to maintain some stability while letting generativity happen (mostly) uninhibited? What do you think?
-Jason


October 27th, 2008 at 7:01 am (#)
I’m surprised there is no reference to Open Source: isn’t the whole platform (to be) opened enough to identify it?
After Apple’s abuse, I certainly understand this can be frightening; I doubt it was in Apple’s or it will be Google’s interest to prevent a legitimate use, and I am positive that without central filtering, badware could use a control mechanism. I’d support a ‘secure’ default, with a choice for more savvy users — but I’m not sure whether a black-hat hacker couldn’t patch that. A clarification of any ban would be needed, whatever is the platform.
November 3rd, 2008 at 3:58 pm (#)
[...] applications. Both phones are not entirely generative in that the companies have the right to terminate an application. However, developers for the Android do not need approval from Google whereas all iPhone apps are [...]
November 3rd, 2008 at 4:22 pm (#)
[...] applications. Both phones are not entirely generative in that the companies have the right to terminate an application. However, developers for the Android do not need approval from Google whereas all iPhone apps are [...]
January 29th, 2009 at 11:44 am (#)
[...] replicated the iPhone’s App Store. There hasn’t been much protest about the Android kill switch, and people might well be okay with pulling apps that pose security problems from the Market [...]
February 1st, 2009 at 10:30 am (#)
Disturbing trend. Apple, definitely, want to keep things hermetically sealed (contrast with their 2004 commercial) yet openness advocates with they large commercial interests seem to change their minds at some point in the game.
Personally, I am willing to ditch any technology that is too restrictive.
April 2nd, 2009 at 2:19 pm (#)
[...] I read the TOS, Google could use its kill switch to yank back even those apps downloaded from third-party websites, but I haven’t heard of [...]