In Gulliver's landing page you can browse the set of currently registered PWAs as depicted in the following landing page snapshot:
If you click on a particular PWA, Gulliver takes you to a detail page showing the results of an evaluation done on that specific PWA using the Lighthouse PWA Analyzer tool (Details page #1), and a view of the associated web app manifest file for the application (Details Page #2):
|Details Page #1||Details Page #2|
Gulliver itself has been implemented as a PWA; therefore it is designed to work well on any kind of device, including desktop web browsers (see landing page), and on mobile devices (see details page).
The following components are required to run the project (tested on macOS):
node --version.) If you have a later version, install the LTS version with
Google Cloud SDK. A set of tools for the Google Cloud Platform (GCP) that you can use to access the Google Compute Engine and the Google Cloud Storage, which are two components of GCP used by Gulliver. (How to verify? Run
Memcached. A distributed memory object caching system. (How to verify? Run
memcached(the command should appear to hang), and then
telnet localhost 11211in a separate terminal. In the
versionit should report the
memcachedversion. If you don't have it, see these instructions to install memcached.)
In addition, you will need to set up a GCP project, and configure OAuth:
Create a Google Cloud Platform project. A GCP project forms the basis of accessing the GCP. Then, run
gcloud initto configure
gcloudlocally, if you get the error "Could not load the default credentials" run
gcloud auth login.
Get the OAuth client id and client secret associated with this project. (How to verify? There's no automatic way, but see Creating a Google API Console project and client ID for how to create one. Make sure you list
http://localhost:8080as one of the
Finally (and optionally), you need a Firebase project, and the Firebase Cloud Messaging "Server key" and "Sender ID":
Create a Firebase project.
Get Firebase Cloud Messaging "Server key" and "Sender ID" associated with this project. Select "Project settings" and then "Cloud Messaging". The URL should be of the form https://console.firebase.google.com/project/$FIREBASE_PROJECT/settings/cloudmessaging. (How to verify? There's no automatic way, but the "Server key" should be a long string of >100 characters, and the "Sender ID" a >10 digit number.)
Clone the GitHub repository:
git clone https://github.com/GoogleChrome/gulliver.git
Switch into the project directory:
Create indexes for the Google Cloud Datastore:
gcloud datastore create-indexes index.yaml
(Optional) Deploy cron jobs for scheduled PWA updates:
gcloud app deploy cron.yaml
Install Memcached and run it on
localhost:11211. Check these installation instructions for guidance.
npm installto install dependencies.
Configure your project either via a config file or environment variables (which override the corresponding keys in the config file). To create a config file, copy the sample config and adjust the values accordingly:
$ cp config/config.example.json config/config.json $ vim config/config.json
Start Gulliver via
Gulliver should now be running at
To verify that everything is working properly you can run the project's tests:
npm testto run lint + tests + coverage report.
npm run mochato run all the tests only.
npm run coverageto run tests + coverage report.
Lighthouse PWA Analyzer
Gulliver reports an evaluation of the "progressiveness" of each registered PWA. This evaluation is done by Lighthouse, which is a tool that runs a set of checks validating the existence of the features, capabilities, and performance that should characterize a PWA. You can learn more about Lighthouse in the GitHub repository, or in this video.
To find out more about what PWAs are and how to go about incorporating the principles of PWAs into the development of your applications, check the following references which provide introductory information and references:
Progressive Web Apps: Documentation entry point. Here you will find several resources to get started developing PWAs
Progressive Web Apps: Escaping Tabs without Losing our Soul: Introductory article with historical perspective
Getting Started with Progressive Web Apps: Sound introduction on the fundamental elements behind the development of PWAs
The Building Blocks of PWAs: Interesting overall view of PWAs.
See LICENSE for more.
This is not a Google product.