/
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

Intel's voice recognition will blow Siri out of the water—because it doesn't use the cloud

because it doesn't use the cloud —  There's a problem with today's voice recognition systems: They're just too slow.  Anyone who has waited in frustration while Siri or Google's Voice Search “thinks” about even the simplest commands knows what I'm talking about.

Quartz Christopher Mims

Context & Ripple Effects

Intel's pitch lands in an assistant market already wrestling with latency: cloud round-trips are why Siri and Google Voice Search 'think' before answering simple commands, and the claim that recognition running locally beats both attacks that bottleneck directly. It also extends a line of thinking from Expect Labs tapping Nuance for predictive computing in late 2012, where anticipating user intent was framed as a way around slow, reactive voice search.

The story travelled unusually far for a technology announcement with no product shipping: pickups at The Verge, ExtremeTech, Geek.com and Gearburn all on or about January 28, 2014 suggest the cloud-versus-on-device framing struck a nerve among outlets covering the assistant wars.

First-order effects

  • Intel positions its silicon as an alternative to the cloud-dependent stacks behind Siri and Google Voice Search, making response latency — not feature count — the comparison point for assistants.
  • Apple and Google face a public benchmark built on their weakest visible metric: the lag users feel on every simple command.

Second-order effects

  • If local processing proves faster than server-side recognition, other chipmakers have reason to bundle speech capabilities into their own platforms, turning assistant quality into a differentiator in device silicon rather than a service layer.
  • Assistant providers relying on data centers must weigh moving more recognition on-device, trading some of the centralization that lets them improve models from aggregate queries.

Third-order effects

  • A shift toward on-device recognition moves value in the voice stack from cloud operators toward whoever owns the processor, foreshadowing assistants embedded in hardware rather than rented from a data center.
  • Whether local models can match the accuracy of cloud-trained systems remains the open question; if they cannot, the speed advantage may prove narrower than Intel's claim implies.

The trend: Voice interfaces are beginning to compete on latency by migrating recognition from the cloud onto local hardware, making chip vendors direct participants in the assistant market.