/
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 posts I/O 2015 schedule: Android M, voice access, ATAP wearables, multi-screen Chromecast games, more

Digging into the Google I/O 2015 schedule: Android M, voice access, and more  —  Google just released the I/O 2015 schedule, and there is a lot of info inside.

Ars Technica Ron Amadeo

Context & Ripple Effects

The I/O 2015 schedule drop is Google laying out its hand three weeks before the keynote: sessions on Android M, voice access, ATAP wearables, and multi-screen Chromecast games give developers the session map before any product is official. It slots into a run-up that already had analysts speculating on Android M, a possible Chromecast 2, and a standalone photos product.

What makes the voice-access sessions notable in hindsight is the arc they start: by the I/O 2017 preview, Assistant and Home were the headline capabilities, meaning the ambient-voice thread planted in 2015 became the throughline of the conference itself.

First-order effects

  • Developers attending I/O now know which tracks to prioritize — Android M sessions signal the next platform APIs they will build against, while ATAP and Chromecast sessions mark Google's experimental hardware bets.
  • The schedule confirms voice access as a first-class developer surface in 2015, giving attendees early access to the interaction model that later coverage shows maturing into Assistant.

Second-order effects

  • Multi-screen Chromecast games put the living-room screen in play as a second-device gaming platform, pressuring the console-and-phone framing competitors had been selling.
  • A public Android M preview cadence forces rival mobile platforms to time their own developer previews against Google's, since the I/O reveal sets the ecosystem conversation each spring — a rhythm still visible when Google schedules I/O years later.

Third-order effects

  • If the pattern holds, I/O functions as an annual re-platforming event: the 2015 voice-access sessions are the seed of the assistant-era conferences seen in 2017 and 2021 coverage, with each year's schedule telegraphing which layer — OS, voice, wearables, TV — Google wants developers to treat as the next default surface.

The trend: Google's I/O schedules have evolved from feature roadmaps into annual signals of which computing surface — phone, voice, wearables, TV — the company intends to make the ecosystem's next center of gravity.