Well-deployed technologies

Foreground Detection

The Page Visibility specification lets developers detect when their application is in the foreground, and thus adapt their operations and resource consumption accordingly.

Technologies in progress


The Web App Manifest specification lets developers group core metadata about a Web application such as its name, icon, preferred start URL, and display mode in a single JSON file. Browsers can leverage this information to propose that the application be installed on the home screen of mobile devices, similar to native applications, and to create a richer user experience.

The Web App Manifest - Application Information Note extends the manifest format with supplementary properties that do not affect how a browser presents an installed web application, but that provides useful metadata for search engines, application catalogs, and stores, such as category hints, age rating, and screenshots.

The Badging API defines a more subtle notification mechanism than Web Notifications, allowing Web applications that have been installed on the device (e.g. through a manifest file) to set an application-wide badge, typically shown next to the application's icon on the home screen, to notify the user when the state of the application has changed and might require their attention (e.g. a new message has arrived).

Offline Web Apps

The Service Workers specification describes a method that enables applications to take advantage of persistent background processing, opening the door to running applications offline.

Not only does Service Workers enables Web applications to work seamlessly offline or in poor network conditions, it also creates a model for Web applications to operate when they have not been opened in a browser window, or even if the browser itself is not running. That ability opens the door for Web applications that run in the background and can react to remotely triggered events.

Remote Notifications

The Push API enables Web applications to subscribe to remote notifications that, upon reception, wake them up. Native applications have long enjoyed the benefits of greater user engagement that these notifications bring.

Sharing content

The share action is a common paradigm on mobile devices to pass content across application boundaries, for instance to post a URL or an image to one's favorite social network application. The Web Share API specification allows a Web application to share text, links and other content to an arbitrary destination of the user's choice. The API is a more focused version of the Web Intents proposal, which was abandoned end of 2012, in part because its genericity triggered user experience issues.

The Web Share Target API proposal allows web applications to declare, in their application manifest, that they can receive content shared from other applications. This allows Web applications, that the user chose to install, to be listed among other native applications in share menus.


Through support for background operations, the Geolocation Sensor specification allows Web applications to be woken up when a device enters a specified geographical area, also known as geofencing.

FeatureSpecification / GroupMaturityCurrent implementations
Select browsers…
PackingWeb Application Manifest
Web Applications Working Group
Working Draft
Web App Manifest - Application Information
Web Applications Working Group
Group Note - informative
Badging API
Web Applications Working Group
Working Draft
Offline Web AppsService Workers 1
Service Workers Working Group
Candidate Recommendation
Remote NotificationsPush API
Web Applications Working Group
Working Draft
Sharing contentWeb Share API
Web Applications Working Group
Proposed Recommendation
Web Share Target API
Web Applications Working Group
Editor's Draft
GeofencingGeolocation Sensor
Devices and Sensors Working Group
Working Draft

Exploratory work


The Web Packaging document describes use cases for a new package format for web sites and applications and outlines such a format.

State transition

Applications running on mobile devices can go through different application states, from running to being idle, paused, stopped, discarded, or terminated. Transitions between these states are triggered by the underlying operating system, and hidden from web applications. The Page Lifecycle proposal seeks to expose application state transitions to applications so that these applications can persist/restore state, enable/disable use of network, etc.

The User Idle Detection document proposes an API for applications to detect when a user becomes idle or when the screen is locked. Applications may use that information to notify other users that the current user is unreachable (e.g. in chat applications), show timely alerts or pause media to save bandwidth when the user is not present.

Seamless navigation

Various sites embed content from a third party origin (e.g. news content) within their own user interface, or load third party content into an iframe to provide a faster, reliable loading experience, which is particularly crucial on mobile devices. One main drawback of this approach is that the third party's origin is not preserved: only the first party's origin appears in the address bar, which makes it difficult for users to identify the provenance and trustworthiness of the content they are browsing. Another drawback is that the third party page cannot leverage client-side resources and permissions that are attached to their origin. Portals is a proposal for enabling seamless navigations between sites or pages. In particular, it enables a page to show another page as an inset and perform a seamless transition between an inset state and a navigated state, thus solving the origin issues mentioned above.

Background execution

The Web Background Synchronization specification builds on top of Service Workers to enable Web applications to keep their user data up to date seamlessly, by running network operations in the background, adjusting to possibly unreliable connections that users often experience on mobile devices.

Background Fetch defines a similar service worker based download and upload mechanism in the background, but allows the background operation to continue, with user visibility, even if the user closes all windows and workers. The specification is specifically tailored to enable downloads/uploads of large assets (podcasts, movies, textures).

Shared resources

An application may run multiple workers at once, and multiple instances of an application may be running concurrently in separate windows. The Web Locks API allows such an application to acquire locks and coordinate usage of shared resources, such as storage, across instances.


MiniApps are applications that run in a hosting application with hybrid native/web capabilities. MiniApps use Web technologies (CSS, JavaScript) although a few common Web technologies are not available for performance or security reasons (e.g. MiniApps usually cannot access the DOM). The runtime also features additional APIs that are more traditionally found in native applications (e.g. contacts API, maps) or application frameworks (e.g. views, router). The trust model of MiniApps also differs from regular Web applications as MiniApps usually need to be reviewed and approved by the hosting platform before users can access them. The MiniApp Standardization White Paper reviews potential standardization areas for MiniApps. The MiniApp Community Group incubates more specific proposals (URI Scheme, Lifecycle, Manifest, Packaging).

FeatureSpecification / GroupImplementation intents
Select browsers…
PackingWeb Packaging
Web Platform Incubator Community Group
State transitionPage Lifecycle
Web Platform Incubator Community Group
User Idle Detection
Web Platform Incubator Community Group
Seamless navigationPortals
Web Platform Incubator Community Group
Background executionWeb Background Synchronization
Web Platform Incubator Community Group
Background Fetch
Web Platform Incubator Community Group
Shared resourcesWeb Locks API
MiniAppsMiniApp Standardization White Paper version 2
MiniApps Working Group

Discontinued features

Application caches
The application cache mechanism was introduced in HTML5 to enable access to Web applications offline through the definition of a manifest of files that the browser is expected to keep in its cache. The feature is well deployed but raises security issues and is extremely limited in terms of how much developers can control what gets cached when. The feature was obsoleted in HTML 5.1, and dropped from HTML 5.2, in favor of the Service Workers specification, which defines a much more powerful approach.
Task Scheduling
The Task Scheduler API made it possible to trigger a task at a specified time via the service worker associated with a Web app. This specification was in scope of the now-closed System Applications Working Group and was shelved as a result.
Geofencing API
The Geofencing API made it possible to wake up a Web app when a device enters a specified geographical area. This work has been discontinued, partly out of struggles to find a good approach to permission needs that such an API triggers to protect users against privacy issues. Through support for background operations, the Geolocation Sensor specification now provides similar functionalities.
Background execution control
User agents will restrict the ability for Web applications to run operations in the background so that users remain in control of what an application can do at all times. The Web Budget API proposed a mechanism by which applications could determine the cost and budget at their disposal to run operations in the background, allowing them to decide whether to perform or postpone these operations. Various parameters could influence the cost of an operation, including whether the device is on battery power and the type of network the device is connected to. This proposal was dropped for lack of adoption and concerns over the design of such an API.