/
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 Reveals ‘The Physical Web,’ A Project To Make Internet Of Things Interaction App-Less

Google's Scott Jenson, an interaction and UX designer who left the company only to return to the Chrome team last November, has revealed a project underway at the company called The Physical Web to provide …

TechCrunch Darrell Etherington

Context & Ripple Effects

The Physical Web extends a decade-long Google argument that the browser, not native software, should be the universal runtime: after retiring Gears for HTML5 in 2009 (waving goodbye to Gears) and proposing Android-style Web Intents baked into Chrome in 2011, the company now wants URLs themselves to be the interface to physical objects. The project sits with the Chrome team, where UX designer Scott Jenson landed after rejoining last November.

The pickup was unusually broad for an early-stage reveal — GitHub, Gigaom, VentureBeat and The Next Web all ran it on day one — which matters because nothing shipped here: this is a positioning shot for how Internet of Things interaction should work before rival platform owners lock in an app-per-device convention.

First-order effects

  • Device makers gain a zero-install path to consumer interaction: any object broadcasting a short URL lets users engage through whatever browser they already have, rather than downloading a vendor app per device.
  • Jenson and the Chrome team, not the Android organization, own the framing — placing Google's IoT interaction bet inside its web platform group at the moment the industry is defaulting to native apps.

Second-order effects

  • Vendors building per-device companion apps face pressure to expose web endpoints alongside or instead of their apps, shifting integration cost from app-store distribution to URL hosting and discovery standards.
  • Mobile platform owners must decide whether to bless browser-based object discovery or defend the native-app funnel that keeps users inside their ecosystems — the same web-versus-native tension Google forced with Web Intents in 2011.

Third-order effects

  • If URL-broadcast becomes a common way people meet connected objects, competition among IoT platforms moves up the stack from radio protocols to whoever controls the discovery layer — the browser and its ranking — echoing how web search consolidated attention once documents went online.
  • A browser-first interaction model also lowers the barrier for small device makers, potentially fragmenting the 'smart object' market away from ecosystems that monetize through mandatory apps.

The trend: Interaction design is drifting from dedicated apps toward an ambient computing layer where the browser discovers and addresses nearby physical objects directly.