Chrome notifications serve Google's strategy by making developers and publishers less reliant on apps
Chrome Notifications, “The Physical Web” And Google's War On Apps — Browser notifications a potential game changer for the mobile web — and Google. — From day one Google has hated apps.
Context & Ripple Effects
This piece lands five days after Google switched on Android support for Chrome notifications, with eBay, Facebook, Pinterest and Product Hunt already signed up as early adopters. The argument it makes is strategic rather than technical: by giving websites an app-like re-engagement channel inside the browser, Google gives publishers a reason to invest in the mobile web instead of native apps — the arena where Apple's App Store rules.
First-order effects
- Publishers and developers among the early adopters gain push-style reach to Android users without building or maintaining native apps, weakening the case for an app-first strategy.
Second-order effects
- Because features like this arrive as Chrome-developed standards, rival browser makers and web developers face pressure to follow Chrome's implementation choices — the pattern later documented in coverage of developers optimizing for standards that first ship in Chrome.
Third-order effects
- A decade on, the same channel needed quality control: Google now ships a feature for automatically disabling notifications from sites users haven't interacted with, showing how a platform Google opened to fight app-store lock-in became a surface it curates itself — consistent with Bloomberg-era concerns about Chromium concentrating effective power over the web.
The trend: The browser is being rebuilt into the web's platform layer, with Google's Chrome-first feature cadence determining what publishers can do without native apps.