/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

The Android fine print: kill switch and other tidbits

An uproar erupted when iPhone users discovered a so-called remote kill switch on their phones — will it spur the same reaction in users of the G1, the first Android phone?  —  In the Android Market terms of service …

Computerworld Nancy Gohring

Context & Ripple Effects

Pre-launch coverage offered sharply different assessments of the G1, from a catalog of its early shortcomings to the case for Android’s competitive potential. The Market terms add a platform-governance question to that launch debate: Android software can be distributed broadly while Google retains authority to remove it from devices.

The iPhone’s comparable capability had already triggered public backlash, making the Android provision consequential not merely as contract language but as a test of whether users accept centralized control over handset software.

First-order effects

  • G1 owners are subject to Android Market terms that permit remote removal of applications, while Google gains a direct mechanism to intervene in software already installed on those phones.
  • Android developers’ access to G1 users is conditional on Market rules, giving Google leverage over applications after distribution as well as before approval.

Second-order effects

  • The Android Market must compete for developer and user trust against the iPhone while both platforms face scrutiny over how much control a platform operator should retain over purchased or installed software.
  • Google’s preloaded applications and services on the G1 make the distinction between an open handset platform and a centrally governed software ecosystem more important to buyers evaluating Android.

Third-order effects

  • If remote-removal powers become standard marketplace practice, smartphone competition will turn partly on governance: the clarity of removal criteria, appeal processes, and limits on operator control—not only device features or app selection.
  • Android illustrates the emerging SDK governance gap, in which broad third-party development can coexist with a platform owner’s unilateral ability to police software on user devices.

The trend: Mobile platforms are pairing third-party app distribution with centralized enforcement powers, making marketplace governance a core competitive and user-trust issue.