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.
- 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.
Explainers: https://github.com/WICG/manifest-incubations/blob/gh-pages/predictable-app-updating.md