Google Announces the Chrome Web Store

Google opened the Chrome Web Store on December 7, 2010, simultaneously with the launch of Chrome OS and the Cr-48, a matte-black developer pilot Chromebook shipped to invited developers. The store distributed three categories of Chrome products: browser extensions (scripts and UI overlays that modified Chrome’s behavior, already available since Chrome 4 in January 2010), browser themes (visual customizations), and web applications (a new category that came in two variants). “Hosted apps” were essentially metadata packages pointing to an existing web URL — an icon, name, description, and a link — that placed a shortcut in Chrome’s New Tab page app launcher and could request additional permissions like offline storage or notification APIs. “Packaged apps” were downloaded to the user’s local Chrome profile and could use Chrome’s local storage APIs, background page capabilities, and hardware access APIs without requiring a network connection, running through Chrome’s own execution environment rather than a traditional OS process. The distinction between hosted and packaged apps was frequently confusing to users: a hosted app for Gmail looked identical in the store to a packaged app for a game, but their offline behavior, storage access, and execution models were completely different.

The Chrome Web Store launched alongside Google’s argument that Chrome OS — a laptop that ran only the Chrome browser with no local application installation beyond Chrome apps — was a viable computing model. The underlying premise was that web applications had advanced sufficiently (through HTML5, local storage, offline caching via AppCache, and the growing capabilities of Chrome’s JavaScript engine V8) to replace native applications for most knowledge worker tasks: email, documents, spreadsheets, communication, and media consumption. The commercial Chromebooks — Samsung Chromebook Series 5 and Acer Chromebook AC700, sold at Best Buy and Amazon starting June 2011 — targeted enterprise and education markets where browser-based productivity was the primary use case and security (automatic updates, no user-installable traditional software, sandbox execution) was a priority. The Chrome Web Store’s extension ecosystem grew substantially: by 2021 it hosted approximately 187,000 active extensions ranging from ad blockers (uBlock Origin, AdBlock Plus) to developer tools (React DevTools, Postman interceptor), productivity tools (Grammarly, LastPass), and accessibility aids.

The packaged Chrome apps format — the one that most resembled native applications — was eventually deprecated. Google announced in 2016 that Chrome Apps (the packaged app format) would be sunset from Chrome on Windows, Mac, and Linux (though not Chrome OS, where they remained relevant longer), with the transition period extending through 2022 for most platforms. The underlying need that Chrome packaged apps addressed — web applications that feel installed, work offline, and access device hardware — was taken over by Progressive Web Apps (PWAs), a standard that emerged from collaboration among browser vendors at the W3C from around 2015 onward. PWAs used Service Workers (for offline caching and background sync), Web App Manifests (for homescreen installation and app-like presentation), and Push Notifications to achieve many of the same goals without requiring Chrome-specific APIs. The Chrome Web Store’s extension marketplace, however, remained central to Chrome’s developer ecosystem through a significant policy transition: in January 2023, Google migrated extensions to Manifest V3 (from V2), a rewritten extension API that limited the powerful declarativeNetRequest permission pattern used by content blockers — a change that prompted significant controversy among privacy and security advocates who argued it would weaken users’ ability to block advertisements and trackers at the browser level.