Contact emails
diby...@google.com,
dmu...@google.com,
fin...@google.com
Explainer
https://github.com/WICG/manifest-incubations/blob/gh-pages/predictable-app-updating.md
Specification
https://www.w3.org/TR/appmanifest/#updating
Summary
Specify an update eligibility algorithm in the manifest spec. This makes the update process more deterministic and predictable, giving the dev more control over whether (and when) updates should apply to existing installations, and allowing removal of the 'update check throttle' that user agents currently need to implement to avoid wasting network resources.
Blink component
Blink>AppManifest
Web Feature ID
manifest
Motivation
- Consistency: Provide a consistent way to detect when a manifest update should happen.
- Preventing unnecessary user interruption: Users should not see an update dialog more than necessary to confirm security-sensitive changes.
- User agent flexibility: It should be possible for users agents to use their judgement to block updates for known bad sites, allow known trusted apps to update without UX, or allow tiny visual changes to icons without requiring UX.
- Developer control: Developers should have more control over when the update dialog may show to users.
- Reduce network traffic: Unnecessary network traffic should be minimized.
Initial public proposal
https://www.w3.org/2022/09/13-webapps-minutes.html#t02
Search tags
pwa,
update,
manifest,
manifest update,
pwa update
TAG review
https://github.com/w3ctag/design-reviews/issues/1076
TAG review status
Issues addressed
Risks
Debuggability
No information provided
Will this feature be supported on all six Blink platforms
(Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
No
No
Flag name on about://flags
chrome://flags/#enable-web-app-predictable-app-updating
Finch feature name
DesktopPWAsPredictableAppUpdating
Rollout plan
Will ship enabled for all users
Requires code in //chrome?
True
Tracking bug
https://issues.chromium.org/issues/403253129
Launch bug
https://launch.corp.google.com/launch/4393456
Availability expectation
Feature is available only in Chrome.
Adoption expectation
This feature paves the way for PWA app migration [1], which is an ask by both first party and third party vendors as an essential feature for PWAs (
crbug.com/380486617).
[1]
https://github.com/WICG/manifest-incubations/blob/gh-pages/pwa-migration-explainer.md
Non-OSS dependencies
Does the feature depend on any code or APIs outside the Chromium
open source repository and its open-source dependencies to
function?
N/A
Estimated milestones
| Shipping on desktop | 143 |
| DevTrial on desktop | 143 |
Anticipated spec changes
Open questions about a feature may be a source of future web compat or
interop issues. Please list open issues (e.g. links to known github
issues in the project for the feature specification) whose resolution
may introduce web compat/interop risk (e.g., changing to naming or
structure of the API in a non-backward-compatible way).
N/A, anticipated spec changes will not be introducing interop risks. Changes are being made on Chrome's end to make PWAs more safer.
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5148463647686656?gate=5181792593903616
Links to previous Intent discussions
Intent to Prototype:
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2B4qT31vY-P2d2e%2Be5F101d_e%2B%3DOEE-%2BnbqxtqHSboeiJFqKOQ%40mail.gmail.com