/
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

With Chrome 57, Progressive Web Apps will appear in Android's app drawer, settings, more

The ambitious goal behind Progressive Web Apps is to allow websites to have the same capabilities and features as a native app, but without the initial download.  Google has been a heavy backer …

9to5Google Abner Li

Context & Ripple Effects

This is the moment Progressive Web Apps stop being a browser feature and start being an OS citizen: with Chrome 57, sites a user has added land in Android's app drawer and settings alongside native installs — no Play Store download required. It lands a year after Henrik Joreteg documented why he left iOS for Android because WebKit's limits kept web apps from feeling native there, making this rollout Google's clearest answer to that gap.

First-order effects

  • Developers with installable web apps suddenly get default home-screen, app-drawer, and settings presence on Android without shipping through the Play Store, collapsing the install friction that favored native apps.
  • Users gain one unified place to manage web and native apps, which makes 'add to home screen' a real alternative to downloading for lightweight use cases.

Second-order effects

  • Apple's WebKit constraints become a visible competitive liability on the exact axis — web apps indistinguishable from native — where Android now demonstrates parity, pressuring the case for loosening them.
  • The Play Store's role as the sole gateway to Android app presence starts to erode for web-first developers, shifting discovery toward the open web and search rather than the store catalog.

Third-order effects

The trend: Operating systems are absorbing web apps as first-class citizens, turning browser vendors into de facto app-platform providers and weakening the native-store gatekeeping model.