Closed Bug 1190388 Opened 9 years ago Closed 6 years ago

[User Story] Update app metadata

Categories

(Firefox OS Graveyard :: Gaia::System::Browser Chrome, defect, P2)

Product:
Firefox OS Graveyard
Component:
Gaia::System::Browser Chrome
Platform:
ARM
Gonk (Firefox OS)
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: benfrancis, Unassigned)

References

Details

(Keywords: feature, Whiteboard: [systemsfe])

User Story

As a user I want my pinned web apps to be kept up to date so I always have the latest name and icon etc.

As a developer I want to provide updates to the metadata of my web app so that I can change the name/icon/display/orientation etc.
As a user I want my pinned web apps to be kept up to date so I always have the latest name and icon etc.

As a developer I want to provide updates to the metadata of my web app so that I can change the name/icon/display/orientation etc.

See also: bug 1183054.

Proposed implementation:
Each time a web app is launched and its start_url is loaded, if the manifest URL linked from that page has changed, or if the cache of the manifest data has expired, the manifest should be re-downloaded and updated in the sites (currently "bookmarks") DataStore. This change will automatically be reflected on the homescreen.

Fetching the manifest should ideally use the proposed getManifest() method on the Browser API from bug 1169633. I'm not sure how we should decide when the cached manifest has expired, whether we can just use the cache headers on the HTTP response or we need to set limits on how frequently or infrequently the manifest is updated.
Priority: -- → P2
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.