/
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

Google releases ARCore Developer Preview 2 and says it is ending support for Project Tango

Augmented reality is a powerful way to bring the physical and digital worlds together.  AR places digital objects and useful information into the real world around us, which creates a huge opportunity …

The Keyword Nikhil Chandhok

Context & Ripple Effects

When Google launched the ARCore preview in August, it was already framed as a retreat from specialized hardware: analysts noted the ARCore SDK is essentially a simplified Tango SDK, rebuilt to run on ordinary Pixel and Galaxy S8 cameras rather than Tango's dedicated depth sensors. Preview 2 plus the formal end of Project Tango makes that pivot official — Google is abandoning its three-year bet on instrumented devices and consolidating Android augmented reality onto a software-only layer that can scale across commodity phones.

The strategic logic is competitive parity with Apple: ARKit reached iPhone developers first, and ARCore only exists to close that gap without waiting for an installed base of Tango-capable hardware. Killing Tango removes the internal rival to its own successor.

First-order effects

  • Developers building on Project Tango must migrate their apps to ARCore or lose platform support, while Android AR developers get a second preview release to build against before general availability.

Second-order effects

  • Phone makers like Samsung are freed from certifying Tango-specific hardware, so AR reach now depends on how fast ARCore expands beyond the initial Pixel and Galaxy S8 target list — and Apple's ARKit head start forces Google to match feature velocity at each release.

Third-order effects

  • If the pattern holds, mobile AR becomes a two-platform software race between ARCore and ARKit fought on existing handsets, with depth sensing delivered through software APIs — as later seen when Google shipped the ARCore Depth API — rather than through proprietary sensor hardware.

The trend: Mobile augmented reality is consolidating from bespoke-hardware experiments into software-only SDKs that run on commodity smartphones, with Google and Apple as the two gatekeepers.