Skip to content

Commit

Permalink
Update use cases.
Browse files Browse the repository at this point in the history
  • Loading branch information
Mugdha Lakhani committed Apr 5, 2019
1 parent 95a8ada commit 5566263
Showing 1 changed file with 19 additions and 21 deletions.
40 changes: 19 additions & 21 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,33 +17,31 @@ If this proposal stands, we plan to extend the [Background Sync](https://wicg.gi
specification to describe this ability as well, and move the document to the standardization track.

## Use cases
Many apps benefit from updating their state and content when the device has
network connectivity, before the user navigates to their web page.
This skips the otherwise slow and laggy experience that the
user would otherwise go through if the app was being updated while being used.

The app can also delight its users by presenting the most up to date content,
right away at launch time.

Here are two main types of updates that are beneficial if done
opportunistically:
Consider a website that's offline enabled. It uses service workers to provide an almost
instantaneous loading experience. However, it may have to show stale content and switch it out
shortly after the user visits the site, once it has downloaded the latest content.
This app will benefit from updating its state and content when the device has network
connectivity, *before* the user navigates to its web page. This way, it can delight its users by
presenting the most up to date content, right away at launch time.

Here are two main types of updates that are beneficial if done opportunistically:
1. Updating state:
This is the data required for the correct functioning of the app. Examples:
a. Updated search index for a search app.
b. Synchronized game scores for the user and her friends for a gaming app.
b. Synchronized game scores for the user and their friends for a gaming app.
c. Updated icons after a UI overhaul of a web app.

2. Updating content:
Periodic content producers can push content to user devices,
to be consumed at a later, more convenient time. Examples:
a. Fresh articles from news and Manga sites.
b. Synchronized photos from other devices, in a photo app.
c. New songs from their favorited artists, in a songs app.

Currently, the Push API enables this, but it requires setting up a server
that speaks the Web Push protocol, and is GDPR compliant. Additional tasks
like resource and certificate management add complexity to this approach.
Periodic Background Sync offers a simpler, more accessible solution.
Periodic content producers can push content to user devices, to be consumed at a later, more
convenient time. Examples:
a. Fresh articles from news sites.
b. List of badges the user has earned, in a fitness app.
c. List of new songs from their favorited artists, in a songs app, to be downloaded using
Background Fetch if the user clicks on "Download".

Currently, the Push API enables this, but it requires setting up a server that speaks the Web
Push protocol, and is GDPR compliant. Additional tasks like resource management add complexity to
this approach. Periodic Background Sync offers a simpler, more accessible solution.

## Why do we care?
* todo
Expand Down

0 comments on commit 5566263

Please sign in to comment.